- 14 8月, 2023 12 次提交
-
-
由 Filip Navara 提交于
-
由 Eirik Tsarpalis 提交于
Improve error message in the new `JsonNode.GetElementIndex()` and `GetPropertyName()` methods. (#90486)
-
由 Thays Grazia 提交于
* Do not use select on debugger-agent * use pool on APPLE os
-
由 Thays Grazia 提交于
* Symbolicate function names on debug callstack * Addressing @radical suggestion * Addressing @radical suggestions. * cleanup --------- Co-authored-by: NAnkit Jain <radical@gmail.com>
-
https://github.com/dotnet/roslyn-analyzers由 dotnet-maestro[bot] 提交于
Microsoft.CodeAnalysis.Analyzers , Microsoft.CodeAnalysis.NetAnalyzers From Version 3.11.0-beta1.23407.1 -> To Version 3.11.0-beta1.23412.1 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 Benjamin Petit 提交于
-
由 Egor Bogatov 提交于
-
由 Marie Píchová 提交于
* Merge pull request #90173 from vseanreesermsft/internal-merge-7.0-2023-08-08-1042 Merging internal commits for release/7.0 * Consume MsQuic release package on Win --------- Co-authored-by: NCarlos Sánchez López <1175054+carlossanlop@users.noreply.github.com> Co-authored-by: NNatalia Kondratyeva <knatalia@microsoft.com>
-
-
由 Eric Erhardt 提交于
- Passing null into the hosting lifetimes' loggerFactory parameters would result in a NRE Contributes to #90400
-
由 Manodasan Wignarajah 提交于
* Add initial changes for COM Aggregation and XAML reference tracking in AOT * Fix dependency list to avoid allocations * Fix issues with finalizer races and issues with allocating memory during GC * Add COM weak reference support * PR feedback on separating reference tracker object fields. Co-authored-by: NAaron Robinson <arobins@microsoft.com> Co-authored-by: NJan Kotas <jkotas@microsoft.com> Co-authored-by: NJeremy Koritzinsky <jkoritzinsky@gmail.com>
-
由 Tarek Mahmoud Sayed 提交于
-
- 13 8月, 2023 9 次提交
-
-
由 Alexander Köplinger 提交于
It is blocking the official build: https://github.com/dotnet/runtime/issues/90466
-
由 dotnet bot 提交于
* Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2228738 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2229389 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2230534 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2231640 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2233112 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2234217 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2235989 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2236160 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2236693 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2238073 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2240179 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2241002 * Localized file check-in by OneLocBuild Task: Build definition ID 679: Build ID 2241178 --------- Co-authored-by: NAlexander Köplinger <alex.koeplinger@outlook.com>
-
由 Sven Boemer 提交于
-
由 Ankit Jain 提交于
* [wasm] build-packages make target - build all the required packages for wbt * WBT: Add more tests for blazor+InvariantGlobalization * Fix test
-
由 Ankit Jain 提交于
-
由 Thays Grazia 提交于
* Do not run this test on Firefox * Disable other test
-
由 Ankit Jain 提交于
Prompted by failures described in https://github.com/dotnet/dnceng/issues/450
-
由 Filip Navara 提交于
* Use custom implementation of _dyld_find_unwind_sections on Apple platforms since it's a private API and it blocks uploads to TestFlight, iOS App Store, and Mac App Store. * Link against local ICU libraries on iOS-like platforms * Update src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.Unix.targets * Add comment * Update src/coreclr/nativeaot/Runtime/unix/UnwindHelpers.cpp Co-authored-by: NJan Kotas <jkotas@microsoft.com> --------- Co-authored-by: NJan Kotas <jkotas@microsoft.com>
-
由 Elinor Fung 提交于
-
- 12 8月, 2023 19 次提交
-
-
由 Павел Харьков 提交于
Fixed error when _hashtableContentsToEnumerate is null. It appears always when using 'Length' property when variable is null. Also reduced nesting.
-
由 dotnet-maestro[bot] 提交于
* Update dependencies from https://github.com/dotnet/arcade build 20230811.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 8.0.0-beta.23409.5 -> To Version 8.0.0-beta.23411.1 * Update dependencies from https://github.com/dotnet/emsdk build 20230811.2 Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100.Transport From Version 8.0.0-rc.1.23411.1 -> To Version 8.0.0-rc.1.23411.2 Dependency coherency updates runtime.linux-arm64.Microsoft.NETCore.Runtime.ObjWriter,runtime.linux-x64.Microsoft.NETCore.Runtime.ObjWriter,runtime.linux-musl-arm64.Microsoft.NETCore.Runtime.ObjWriter,runtime.linux-musl-x64.Microsoft.NETCore.Runtime.ObjWriter,runtime.win-arm64.Microsoft.NETCore.Runtime.ObjWriter,runtime.win-x64.Microsoft.NETCore.Runtime.ObjWriter,runtime.osx-arm64.Microsoft.NETCore.Runtime.ObjWriter,runtime.osx-x64.Microsoft.NETCore.Runtime.ObjWriter,runtime.linux-arm64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.linux-x64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.linux-musl-arm64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.linux-musl-x64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.win-arm64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.win-x64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.osx-arm64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.osx-x64.Microsoft.NETCore.Runtime.JIT.Tools,runtime.linux-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.linux-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools,runtime.linux-musl-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.linux-musl-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools,runtime.linux-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.linux-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools,runtime.linux-musl-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.linux-musl-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools,runtime.win-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.win-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools,runtime.osx-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.osx-arm64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools,runtime.osx-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Sdk,runtime.osx-x64.Microsoft.NETCore.Runtime.Mono.LLVM.Tools From Version 16.0.5-alpha.1.23401.4 -> To Version 16.0.5-alpha.1.23408.1 (parent: Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100.Transport --------- Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 Steve Pfister 提交于
-
由 Jakob Botsch Nielsen 提交于
The inliner heuristics do not take into account that inlining methods causes type/method loading of the generic context. After #88749 this can quickly cause significant resources to be consumed as part of inlining when polymorphic recursion is involved (the blow-up can be exponential, as we see in the failing test under jitstress). This PR adds another safe-guard to the recursive inlining check in terms of a complexity limit on the generic context of the inline candidate. Fix #90144
-
由 Stephen Toub 提交于
* Remove all use of <Nullable>annotations</Nullable> We've inadvertently shipped multiple libraries with incorrect nullable reference type annotations because: a) Their ref assemblies aren't actually being shipped, and/or b) Their src projects using `<Nullable>annotations</Nullable>` `<Nullable>annotations</Nullable>` means "I'm nullable annotated but don't validate them", which means consumers of these libraries see annotations that we haven't thoughtfully added or reviewed. This removes all use of it and gets us back to a place where we're only shipping nullable annotations for libraries where we've done the work to ensure they're correct. We can subsequently finish annotating these stragglers. * Don't disable LibraryImportGenerator when nullable is disabled * Add #nullable enable to LibraryImportAttribute file for polyfill scenarios. * Disable LibraryImportGenerator on ILCompiler.TypeSystem.Tests assemblies. Convert a DllImport in HostWriter that now gets the polyfill experience. --------- Co-authored-by: NEric StJohn <ericstj@microsoft.com> Co-authored-by: NJeremy Koritzinsky <jekoritz@microsoft.com>
-
由 Eric StJohn 提交于
* Add DiagnosticDescriptorHelper Create a helper method that formats and sets the helpLink for DiagnosticDescriptors * Add HelpLinkUris to ILLink * Handle different DiagnosticCategories
-
由 Steve Pfister 提交于
This change adds CLI telemetry for common mobile and wasm scenarios. Total app size is another element we plan on tracking and that will be added in a follow up. Fixes https://github.com/dotnet/runtime/issues/88844
-
由 Jackson Schuster 提交于
-
由 Jackson Schuster 提交于
Prefix type names with global and use static TypeSyntax and NameSyntax instead of Parse(Type)Name (#90339) * Prefix type names with global and use static TypeSyntax and NameSyntax instead of Parse(Type)Name
-
由 Tarek Mahmoud Sayed 提交于
-
由 Ankit Jain 提交于
The following commit caused workload to be required for a blazor app when `InvariantGlobalization==true`, but this is not required. ``` commit 26ae0978 Author: Ankit Jain <radical@gmail.com> Date: Thu Aug 10 23:39:10 2023 -0400 [wasm] Fix up conditions to trigger relink, and require `wasm-tools` workload (#89754) ``` And this broke some sdk tests.
-
由 jthorborg 提交于
* Relaxing constraints of System.GC.AllocateArray<T>. It's now possible to allocate pinned and default-initialized arrays that contain references. Fix #48703 * Adding coverage of GC.AllocateArray with ref types. Added a test that pins a reference type array and resolves references to indices with pointer arithmetic, checking that modifications are visible back in the original array. Test #48703 * Mono/NativeAOT relaxing of System.GC.AllocateArray<T>. * Relaxed GC.AllocateUninitializedArray for ref types as well. This was done by deferring reference types to GC.AllocateArray to avoid potential memory issues with the GC + uninitialized memory. The API only promises to avoid initialization if possible, anyway. Refactored tests to parametrically exercise these new relaxed constraints. * Simplifiy conditionals in AllocateUninitializedArray. Relying on internal implementation zeroing refs if necessary. * Also simplify path for NativeOAT. Mono already piggybacks on the AllocateArray path anyway. * Simplify pinning paths. All conditional paths in GC.Allocate*Array now handle pinning unconditionally out of the main branch. * Don't use `var` if type name doesn't exist explicitly on right-hand side * PR feedback for using terse method tables and JIT intrinsics for GC array allocation that should be slightly faster. * Changed EmbeddedValueType and added comment. After a longer discussion, settled on a slightly augmented suggestion that isn't as controversial as the prior one. * Fixing signature for `RhAllocateNewArray` in NativeAOT to directly use a `MethodTable*` * Adding explicit structlayout to silence warning for EmbeddedValueType in GCTests, and improved the comment. --------- Co-authored-by: NJan Kotas <jkotas@microsoft.com>
-
由 Koundinya Veluri 提交于
- A previous change that was serviced back changed session-local named mutexes to be user-specific by restricting the permissions of the session directories and files under them, and adding the sticky bit to some directoires. A compat issue arose from that change, as the session directories have the session ID in their name and session IDs can be reused between different users. The current plan that we have discussed is to revert the change and service back the revert, which also restores the intended behavior, and offer user-specific mutexes as a new feature in a future .NET that would satisfy some user scenarios in a better way. - This PR reverts the previous change (first commit) and restores one change from the previous change (second commit) to improve backward compatibility due to differences in permissions for session directories before and after the change - Fixes https://github.com/dotnet/runtime/issues/80619
-
由 Poppyto 提交于
* first XOR Linq implemetation * replace classic allocation by stack allocation for ReadByte * replace classic allocation by stack allocation for ReadByte & WriteByte * replace classic allocation by stack allocation for ReadByte/CopyToAsync * add missing ConfigureAwait(false) on ReadAsync * replace classic allocation by stack allocation for ReadByte/WriteByte * Revert "first XOR Linq implemetation" This reverts commit 449fddec66b3311866dc1e57c07ad7127e8039ff. * indent fix * rollback stackalloc on async methods * missing char * fix ConfigureAwait * rollback ReadByte optim (degrade perfs) * variablename fix * missing comment * rollback Stream allocations * missing arguments * add Write(ReadOnlySpan<byte>) method * better initialize Span * add CRLF * resolve comments * simplification call method Write * Update src/libraries/System.Private.DataContractSerialization/src/System/Runtime/Serialization/Json/JsonEncodingStreamWrapper.cs replace Span by ReadOnlySpan Co-authored-by: NMichał Petryka <35800402+MichalPetryka@users.noreply.github.com> * remove trailing whitespace * Update src/libraries/System.Private.DataContractSerialization/src/System/Runtime/Serialization/Json/JsonEncodingStreamWrapper.cs Co-authored-by: NStephen Toub <stoub@microsoft.com> * Update src/libraries/System.Private.DataContractSerialization/src/System/Runtime/Serialization/Json/JsonEncodingStreamWrapper.cs Co-authored-by: NStephen Toub <stoub@microsoft.com> --------- Co-authored-by: NMichał Petryka <35800402+MichalPetryka@users.noreply.github.com> Co-authored-by: NStephen Toub <stoub@microsoft.com>
-
由 Daniel Svensson 提交于
* Use ConcurrentDictionary to avoid lock contention when serializing using DataContractSerializer * Improve concurrency for GetId * Prevent allocating multiple slots in s_dataContractCache for the same typeHandle * Use RuntimeTypeHandle as key in dictionary * add readonly * Remove usage of lazy * revert whitespace changes * Use RuntimeTypeHandle.Value as key instead of RuntimeTypeHandle * Apply same perf improvement to JDCS; Remove Int/TypeHandleRef silliness that we no longer need. --------- Co-authored-by: NSteve Molloy <smolloy@microsoft.com>
-
由 Eirik Tsarpalis 提交于
* Improve debugging for configuration lists. * Add missing DebuggerBrowsable.Never annotations. * Add DebuggerBrowsableState.Never to a few internal getters that may throw. * Simplify JsonPropertyInfo DebuggerDisplay * Ensure debugger display matches API name.
-
由 Alexander Köplinger 提交于
We noticed that ARC isn't enabled for System.Globalization.Native code but we aren't properly doing manual memory management by calling `release`. Enable ARC for the System.Globalization.Native ObjC code so it is handled automatically by the compiler. Disable it for System.Native code since that one is less complex and we can manually manage it. We need to wrap all public entrypoints to the library in `@autoreleasepool` blocks so that the releasing of autoreleased objects occurs at the end of the block, rather than at some undetermined point in the future (and we don't even know if we have an autorelease pool in the thread).
-
由 Milos Kotlar 提交于
This PR adds support for Native AOT compilation on Helix. It improves test coverage for Mono and Native AOT by running functional tests on Helix. The proxy project is updated with Native AOT props and apple build targets are updated to support Native AOT compilation. Additionally, it simplifies the sample app by utilizing the shared Apple targets.
-
由 Ankit Jain 提交于
This reverts commit bbe40f8c. This caused perf pipeline runs to break. But https://github.com/dotnet/performance/pull/3251 from @caaavik-msft, along with this revert will fix the issue. Issue: https://github.com/dotnet/runtime/issues/90420
-