Microsoft.SourceBuild.Intermediate.cecil , Microsoft.DotNet.Cecil
From Version 0.11.5-alpha.25206.5 -> To Version 0.11.5-alpha.25213.4
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
iOSSimulator, tvOSSimulator, MacCatalyst pipelines are migrated to:
- `osx.15.amd64.open`
- `osx.14.arm64.open` (until `osx.15.arm64.open` has enough machines)
## Newly failing test scenarios
Some new failures were discovered during the migration. The tests were disabled and tracking issues were open to monitor progress for enablement.
- System.Net.Sockets.Tests.SocketOptionNameTest.MulticastInterface_Set_AnyInterface_Succeeds
- System.IO.IsolatedStorage
- System.IO. MemoryMappedFiles
- System.Net.Sockets.Tests.SendTo_.*.Datagram_UDP_AccessDenied_Throws_DoesNotBind
* Fixing get incomplete context information and assigning invalid information to the context later.
* Fixing the copy and paste.
* remove extra ;
---------
Co-authored-by: Thays Grazia <thaystg@gmail.com>
* Fix dump_processor_state debug code to compile and work on Android (#112970)
Fix typo in GC bridge comparison message (SCCS -> XREFS)
* [mono] Add a few bridge tests (#113703)
* [mono][sgen] Fix DUMP_GRAPH debug option build for tarjan bridge
* [mono][sgen] Don't create ScanData* during debug dumping of SCCs
It serves no purpose and it would later crash the runtime since we didn't patch the lockword back in place.
* [mono][sgen] Fix some null deref crashes in DUMP_GRAPH debug option
* [mono][tests] Add bridge tests
These are ported from some of the bridge tests we had on mono/mono. In order to test them we compare between the output of the new and the tarjan bridge.
* Fix an edge case in the Tarjan GC bridge that leads to losing xref information (#112825)
* Fix an edge case in the Tarjan SCC that lead to losing xref information
In the Tarjan SCC bridge processing there's a color graph used to find out
connections between SCCs. There was a rare case which only manifested when
a cycle in the object graph points to another cycle that points to a bridge
object. We only recognized direct bridge pointers but not pointers to other
non-bridge SCCs that in turn point to bridges and where we already calculated
the xrefs. These xrefs were then lost.
* Add test case to sgen-bridge-pathologies and add an assert to catch the original bug
* Add review
---------
Co-authored-by: Vlad Brezae <brezaevlad@gmail.com>
* [SGen/Tarjan] Handle edge case with node heaviness changing due to deduplication (#113044)
* [SGen/Tarjan] Handle edge case with node heaviness changing due to deduplication
Do early deduplication
Fix Windows build
Add test cases to sgen-bridge-pathologies
* Move test code
* Remove old code
* Add extra check (no change to functionality)
* Disable test on wasm
---------
Co-authored-by: Vlad Brezae <brezaevlad@gmail.com>
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Microsoft.DotNet.HotReload.Utils.Generator.BuildTool
From Version 9.0.0-alpha.0.25174.2 -> To Version 9.0.0-alpha.0.25209.2
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
Microsoft.SourceBuild.Intermediate.cecil , Microsoft.DotNet.Cecil
From Version 0.11.5-alpha.25173.2 -> To Version 0.11.5-alpha.25206.5
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/xharness build 20250403.2
Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 9.0.0-prerelease.25167.9 -> To Version 9.0.0-prerelease.25203.2
* Update dependencies from https://github.com/dotnet/xharness build 20250407.3
Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 9.0.0-prerelease.25167.9 -> To Version 9.0.0-prerelease.25207.3
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/emsdk build 20250404.2
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.5-servicing.25203.2 -> To Version 9.0.5-servicing.25204.2
* Update dependencies from https://github.com/dotnet/emsdk build 20250407.3
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.5-servicing.25203.2 -> To Version 9.0.5-servicing.25207.3
* Update dependencies from https://github.com/dotnet/emsdk build 20250409.3
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.5-servicing.25203.2 -> To Version 9.0.5-servicing.25209.3
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
I noticed this while looking at an issue in the 9.0 branch with latest clang which runs into a couple warnings fixed in main with https://github.com/dotnet/runtime/pull/108888.
We intentionally don't set `-Werror` in release branches to avoid breaking the build when newer compilers add warnings via 37e4d45236/eng/native/configurecompiler.cmake (L564-L567)
However this didn't work because msbuild's WarnAsError was still reading the console output of the native build and upgrading any line with "warning: " to an msbuild error and breaking the build.
Suppress this by setting IgnoreStandardErrorWarningFormat="true" on the Exec call. We already did this in the coreclr and mono runtime builds, we just missed it in libs.native.
cmake 4.0 no longer sets the CMAKE_OSX_SYSROOT variable for macOS targets: https://cmake.org/cmake/help/v4.0/release/4.0.html#other-changes
> Builds targeting macOS no longer choose any SDK or pass an -isysroot flag to the compiler by default. Instead, compilers are expected to choose a default macOS SDK on their own. In order to use a compiler that does not do this, users must now specify -DCMAKE_OSX_SYSROOT=macosx when configuring their build.
We need to stop passing the variable to swiftc in that case and rely on the default behavior.
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
* Update dependencies from https://github.com/dotnet/emsdk build 20250402.2
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25177.1 -> To Version 9.0.4-servicing.25202.2
* Update dependencies from https://github.com/dotnet/emsdk build 20250403.2
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25177.1 -> To Version 9.0.5-servicing.25203.2
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Microsoft.SourceBuild.Intermediate.sdk , Microsoft.DotNet.ApiCompat.Task
From Version 9.0.104-servicing.25111.36 -> To Version 9.0.105-servicing.25164.42
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
Microsoft.CodeAnalysis.Analyzers , Microsoft.CodeAnalysis.NetAnalyzers
From Version 3.11.0-beta1.25123.3 -> To Version 3.11.0-beta1.25173.3
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/hotreload-utils build 20250313.2
Microsoft.DotNet.HotReload.Utils.Generator.BuildTool
From Version 9.0.0-alpha.0.25153.2 -> To Version 9.0.0-alpha.0.25163.2
* Update dependencies from https://github.com/dotnet/hotreload-utils build 20250324.2
Microsoft.DotNet.HotReload.Utils.Generator.BuildTool
From Version 9.0.0-alpha.0.25153.2 -> To Version 9.0.0-alpha.0.25174.2
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* [Apple mobile] Enable trimming on build machines to match ILLink features (#110966)
* Disable failing tests
* Add DataSetXmlSerializationIsSupported to PlatformDetection
There are some `on pull_request_target types` in the label checking yml files that were removed but they are actually necessary, so the labeler keeps working after for example: pushing new commits, pressing the update the branch, closing and opening the PR.
* [9.0] Ensure libnethost isn't built with LTCG
* Move configure include into the pal as that's the only place that uses it.
* It's the other configure file that was causing problems, fix how that one is set up.
Microsoft.SourceBuild.Intermediate.roslyn , Microsoft.CodeAnalysis , Microsoft.CodeAnalysis.CSharp , Microsoft.Net.Compilers.Toolset
From Version 4.12.0-3.25124.2 -> To Version 4.12.0-3.25173.5
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/xharness build 20250313.3
Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 9.0.0-prerelease.25113.3 -> To Version 9.0.0-prerelease.25163.3
* Update dependencies from https://github.com/dotnet/xharness build 20250317.9
Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 9.0.0-prerelease.25113.3 -> To Version 9.0.0-prerelease.25167.9
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/cecil build 20250312.2
Microsoft.SourceBuild.Intermediate.cecil , Microsoft.DotNet.Cecil
From Version 0.11.5-alpha.25112.2 -> To Version 0.11.5-alpha.25162.2
* Update dependencies from https://github.com/dotnet/cecil build 20250316.5
Microsoft.SourceBuild.Intermediate.cecil , Microsoft.DotNet.Cecil
From Version 0.11.5-alpha.25112.2 -> To Version 0.11.5-alpha.25166.5
* Update dependencies from https://github.com/dotnet/cecil build 20250323.2
Microsoft.SourceBuild.Intermediate.cecil , Microsoft.DotNet.Cecil
From Version 0.11.5-alpha.25112.2 -> To Version 0.11.5-alpha.25173.2
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Carlos Sánchez López <1175054+carlossanlop@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/emsdk build 20250313.3
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25157.2 -> To Version 9.0.4-servicing.25163.3
* Update dependencies from https://github.com/dotnet/emsdk build 20250314.2
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25157.2 -> To Version 9.0.4-servicing.25164.2
* Update dependencies from https://github.com/dotnet/emsdk build 20250317.2
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25157.2 -> To Version 9.0.4-servicing.25167.2
* Update dependencies from https://github.com/dotnet/emsdk build 20250320.1
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25157.2 -> To Version 9.0.4-servicing.25170.1
* Update dependencies from https://github.com/dotnet/emsdk build 20250321.1
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25157.2 -> To Version 9.0.4-servicing.25171.1
* Update dependencies from https://github.com/dotnet/emsdk build 20250327.1
Microsoft.SourceBuild.Intermediate.emsdk , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100 , Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
From Version 9.0.4-servicing.25157.2 -> To Version 9.0.4-servicing.25177.1
Dependency coherency updates
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 19.1.0-alpha.1.25113.2 -> To Version 19.1.0-alpha.1.25163.1 (parent: Microsoft.NET.Workload.Emscripten.Current.Manifest-9.0.100.Transport
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Update dependencies from https://github.com/dotnet/icu build 20250312.2
Microsoft.NETCore.Runtime.ICU.Transport
From Version 9.0.0-rtm.25157.1 -> To Version 9.0.0-rtm.25162.2
* Update dependencies from https://github.com/dotnet/icu build 20250313.1
Microsoft.NETCore.Runtime.ICU.Transport
From Version 9.0.0-rtm.25157.1 -> To Version 9.0.0-rtm.25163.1
* Update dependencies from https://github.com/dotnet/icu build 20250314.1
Microsoft.NETCore.Runtime.ICU.Transport
From Version 9.0.0-rtm.25157.1 -> To Version 9.0.0-rtm.25164.1
* Update dependencies from https://github.com/dotnet/icu build 20250317.3
Microsoft.NETCore.Runtime.ICU.Transport
From Version 9.0.0-rtm.25157.1 -> To Version 9.0.0-rtm.25167.3
* Update dependencies from https://github.com/dotnet/icu build 20250320.1
Microsoft.NETCore.Runtime.ICU.Transport
From Version 9.0.0-rtm.25157.1 -> To Version 9.0.0-rtm.25170.1
* Update dependencies from https://github.com/dotnet/icu build 20250327.1
Microsoft.NETCore.Runtime.ICU.Transport
From Version 9.0.0-rtm.25157.1 -> To Version 9.0.0-rtm.25177.1
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Larry Ewing <lewing@microsoft.com>
Backport of https://github.com/dotnet/runtime/pull/113140
Issue #109410 appears to be a case where klass is 0 when we perform an isinst operation, but the cache and obj are nonzero and look like valid addresses. klass is either a compile-time (well, jit-time) constant or being fetched out of the cache (it looks like it can be either depending on some sort of rgctx condition).
This PR adds null checks in two places along with a memory barrier in the location where we believe an uninitialized cache is being published to other threads.
---------
Co-authored-by: Katelyn Gadd <kg@luminance.org>
* Trying to add user agent header.
* Test another way
* Change server to httpbin
* Update Http2NoPushHost and add Http2NoPushGetUris for improved testing
---------
Co-authored-by: Roman Konecny <rokonecn@microsoft.com>
This can trip up users that have enabled floating point exceptions.
While we don't generally support changing the exception modes we also
can easily avoid dividing by zero here.
Addresses #113369
Co-authored-by: Andy Ayers <andya@microsoft.com>
* Use FLS detach as thread termination notification on windows.
* use _ASSERTE_ALL_BUILDS
* one more case
* InitFlsSlot throws per convention used in threading initialization
* OsDetachThread could be void
* Update src/coreclr/vm/ceemain.cpp
* ensure CoInitialize
* Asserts to fail deterministically.
* comments
* scope the failfast to Windows and tweak the comments a bit.
* better assert
* Apply suggestions from code review
* Undo unnecessary finalizer thread changes
* reverse the failfast condition
* handle destruction of unattached threads
* PR feedback
* Update src/coreclr/vm/ceemain.cpp
* set g_fComStarted as soon as we call CoInitialize
* Naming nit
* fix a typpo + better comment
---------
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
