Microsoft.NET.ILLink.Tasks
 From Version 7.0.100-1.22158.1 -> To Version 7.0.100-1.22160.1
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

* Update dependencies from https://github.com/dotnet/runtime-assets build 20220310.1

Microsoft.DotNet.CilStrip.Sources , System.ComponentModel.TypeConverter.TestData , System.Drawing.Common.TestData , System.IO.Compression.TestData , System.IO.Packaging.TestData , System.Net.TestData , System.Private.Runtime.UnicodeData , System.Runtime.Numerics.TestData , System.Runtime.TimeZoneData , System.Security.Cryptography.X509Certificates.TestData , System.Text.RegularExpressions.TestData , System.Windows.Extensions.TestData
 From Version 7.0.0-beta.22128.1 -> To Version 7.0.0-beta.22160.1

* Update dependencies from https://github.com/dotnet/roslyn-analyzers build 20220310.2

Microsoft.CodeAnalysis.NetAnalyzers
 From Version 7.0.0-preview1.22157.1 -> To Version 7.0.0-preview1.22160.2
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

thta => that

* Remove duplicated code - I know that tests should be descriptive, but repeating 100 times that we want to capture output doesn't feel necessary.
* For some of them move more stuff into the shared test state - this improves perf as we avoid repeating the setup (copying files around) for each test case, we do it once for the entire class
I also changed some of the tests to "Theory" as it's easier to read that way.
  * `SDKLookup.cs` - moved most of the state in to the shared state to speed up the tests.

* Adding more cases into the "theory" tests
  * Most notably for the framework resolution I added variations on the TFM (which will be needed when we implement disable of MLL)
* Adding new tests mostly around "list runtimes" (various forms), "list sdks" (various forms) and errors (which also list runtimes or sdks)

* Ported all of the `MultiLevelLookupFramework` tests over to the `FrameworkResolution` and `DependencyResolutions` suites which have a more robust test infra and can run the same tests much faster. Along the way I added lot more variations on top of the existing tests:
  * `PerAssemblyVersionResolutionMultipleFrameworks.cs` - this is actually not an MLL test, but I moved it to the new infra to make it much faster
  * `MultipleHives.cs` - MLL framework resolution tests

For SDK resolution I kept the `MultiLevelSDKLookup.cs` just removed code duplication and added new variants.

For the core reviewers: I promise I didn't remove any single test case in spirit with these exceptions:

* We had tests which validated that framework resolution is not affected by frameworks in current directory and also by frameworks in the user's directory. I left some basic test for the current directory check, but I completely removed the user's directory variant as the product simply doesn't have any code around that anymore.

* Remove "user" directory from SDK resolution tests

The product simply doesn't have any knowledge about user directory SDK lookup, so there's little value in testing for it (even though the test expects it to not have any impact).
Co-authored-by: NElinor Fung <elfung@microsoft.com>

* Update repo CMake configuration to target /W4 by default

Disable all failing warnings.

* Mono API tests only use W3

* [metadata] Avoid realloc and memcpy when >1 gparams on generics

* Read the first gparam row again at the beginning of the second pass

[main] Update dependencies from dotnet/linker

This changes the one-shot decryption to allow decrypting directly in to user-supplied buffers, even in the presence of padding, so that a copy and CryptoPool rental can be avoided.

If the buffer is large enough to accommodate the padding, then decrypt directly in to the supplied buffer, zero the padding, and indicate the de-padded amount in bytesWritten.

If the buffer is possibly large enough, then decrypt all but the last block in to the buffer, and do the last block on the stack. If the de-padded amount in the stack is small enough, then copy the remaining. If it is too large, then zero everything in the user buffer.

* Add table of testing configurations

* Remove "cross" from specification

* Overhaul how regex generated code is structured

* Address PR feedback

* Change parser to return RegexMethod

Clean up how the data is structured.

* Add a test for same method name in multiple types

* Add arm64 intrinsics for Narrow

* Fix integer types

* Fix more issues with integer types

* Add some comments

* Nit

* Change var names

* Fix format

* Fix format again

This PR contributes to  #64072

Added intrinsics for following operators
- Operator *
- Operator /
- Operator |
- Operator &
- Operator ^
- Unary operator -
- Unary operator ~
Co-authored-by: NFan Yang <yangfan@microsoft.com>

We never read that field in the runtime and it was causing unnecessary disk IO during startup (5ms on my iOS device).
It was also never set on Windows already.

System.Net.MsQuic.Transport
 From Version 7.0.0-alpha.1.22159.1 -> To Version 7.0.0-alpha.1.22160.2
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

* Use StartsWith(..., OrdinalIgnoreCase) in RegexCompiler / source generator

When we encounter a sequence of sets representing case-insensitive ASCII, we can simplify the code generated to just call StartsWith, which both makes it more readable but also takes advantage of the new JIT optimization to lower that into efficient vectorized comparisons based on the supplied literal.

This also cleans up some formatting in the source generator emitted code to make things much more concise and less noisy.

* Address PR feedback

* disable timing out test on mono

* Update src/libraries/System.Text.Json/tests/System.Text.Json.Tests/Serialization/CustomConverterTests/CustomConverterTests.cs

* Clean up NonBacktracking DgmlWriter

* Address PR feedback, clean up some lang=regex usage, fix a test failure

* Update dependencies from https://github.com/dotnet/arcade build 20220307.6

Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat , Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.GenAPI , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.GenFacades , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.Helix.Sdk
 From Version 2.5.1-beta.22154.3 -> To Version 2.5.1-beta.22157.6

* Update dependencies from https://github.com/dotnet/icu build 20220307.1

Microsoft.NETCore.Runtime.ICU.Transport
 From Version 7.0.0-preview.3.22128.1 -> To Version 7.0.0-preview.3.22157.1

* Update dependencies from https://github.com/dotnet/xharness build 20220307.2

Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
 From Version 1.0.0-prerelease.22153.2 -> To Version 1.0.0-prerelease.22157.2

* Update dependencies from https://github.com/dotnet/roslyn-analyzers build 20220307.1

Microsoft.CodeAnalysis.NetAnalyzers
 From Version 7.0.0-preview1.22153.1 -> To Version 7.0.0-preview1.22157.1

* Update dependencies from https://github.com/dotnet/hotreload-utils build 20220307.2

Microsoft.DotNet.HotReload.Utils.Generator.BuildTool
 From Version 1.0.2-alpha.0.22128.2 -> To Version 1.0.2-alpha.0.22157.2

* Update dependencies from https://github.com/dotnet/llvm-project build 20220307.1

runtime.win-x64.Microsoft.NETCore.Runtime.ObjWriter , runtime.win-arm64.Microsoft.NETCore.Runtime.ObjWriter , runtime.osx.10.12-x64.Microsoft.NETCore.Runtime.ObjWriter , runtime.osx.11.0-arm64.Microsoft.NETCore.Runtime.ObjWriter , runtime.linux-x64.Microsoft.NETCore.Runtime.ObjWriter , runtime.linux-musl-x64.Microsoft.NETCore.Runtime.ObjWriter , runtime.linux-musl-arm64.Microsoft.NETCore.Runtime.ObjWriter , runtime.linux-arm64.Microsoft.NETCore.Runtime.ObjWriter
 From Version 1.0.0-alpha.1.22128.1 -> To Version 1.0.0-alpha.1.22157.1

* Use full names for GenericHandler passed to xharness

* Update dependencies from https://github.com/dotnet/msquic build 20220309.1

System.Net.MsQuic.Transport
 From Version 7.0.0-alpha.1.21529.3 -> To Version 7.0.0-alpha.1.22159.1

* Update dependencies from https://github.com/dotnet/xharness build 20220310.1

Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
 From Version 1.0.0-prerelease.22153.2 -> To Version 1.0.0-prerelease.22160.1
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: NAnkit Jain <radical@gmail.com>

* reproduce issue: collecting disposables even if composite token has alredy been changed

* stop collecting disposables if composite token has already been changed

* Update src/libraries/Microsoft.Extensions.Primitives/tests/CompositeChangeTokenTest.cs
Co-authored-by: NEric Erhardt <eric.erhardt@microsoft.com>

* Update src/libraries/Microsoft.Extensions.Primitives/tests/CompositeChangeTokenTest.cs
Co-authored-by: NEric Erhardt <eric.erhardt@microsoft.com>
Co-authored-by: NEric Erhardt <eric.erhardt@microsoft.com>

Fixes #44689

As of #65148, libraries use different approach to handling OpenSSL errors. The original assert which would be hit if a previous operation left errors in the queue is no longer necessary as all OpenSSL calls are prepended by `ERR_clear_error()` to make sure the latest (and most relevant) error is reported.

Fix the accounting for gen 1 allocations by taking into account what has been already consumed in this GC. (#60248)

Details:

In gen 1 GCs, we recompute the budget at the end of the GC. However, the amount consumed in the current GC is nowhere taken into account. That causes us to do at most alternate gen 0 and gen 1 GCs, we cannot do back-to-back gen 1 GCs.

If we take the gen 1 budget as the amount of memory we are aiming to be used for gen 1, then it seems illogical to just drop the amount used in this GC on the floor.

The fix is to actually subtract the amount of gen 1 budget used in this GC from dd_new_allocation for gen 1. This is a bit awkward for server GC, because we even out the budget and the amount to subtract from dd_new_allocation across heaps after having computed it for each heap individually.

This should help determine where time is being spent in long-running
tasks such as PMI or crossgen2 collections in the CI system.

Also, run a `dotnet --info` command to verify the version of the CLI we are running.

* Revert "Do not mark implicit byrefs with GTF_GLOB_REF (#66266)"

This reverts commit 0a684281. This is
currently not safe to do in the JIT because we clear out address
exposure information in fgRetypeImplicitByRefArgs() and thus do not have
the necessary information in morph to know if indirections off of
implicit byrefs are global or not.

* Add a test

Exit the inner loop every now and then to do a timeout check.

Downgrade the Roslyn version used by the Regex source generator to be 4.0.1 instead of 4.2.0 (#66423)

* Downgrade the Roslyn version used by the Regex source generator to be 4.0.1 instead of 4.2.0

* Update src/libraries/System.Text.RegularExpressions/gen/System.Text.RegularExpressions.Generator.csproj
Co-authored-by: NJeremy Koritzinsky <jkoritzinsky@gmail.com>
Co-authored-by: NJeremy Koritzinsky <jkoritzinsky@gmail.com>

Adds System.Decimal.Scale, a property that
returns the scaling factor of the decimal.

Closes #65074.

* From vm/

* From util/

* From debug/

* GCInfo related

Use MAXDWORD instead of DWORD_MAX.
Remove DWORD_MAX from pal, since it is not used anywhere.

Currently, the `runtime-coreclr superpmi-replay` pipeline is run
when a JIT change is merged. This change moves the checking to happen
on the PR pre-merge, as a requirement for merging.