* Store the result in the return local in native-to-managed IL stubs.

* Unformat includes

* Convert over StandardOleMarshalObject to use either source-generated or manual interop.

* Apply suggestions from code review
Co-authored-by: NAaron Robinson <arobins@microsoft.com>
Co-authored-by: NAaron Robinson <arobins@microsoft.com>

* Setup testing jobs, change repo to test perf repo, and added apk-name parameter to pre.py for mobile scenarios.

* Update dotnet install type to be daily. This matches the link for installing net 6.0 in the maui contributing dev requirements list.

* Try lowercase package name.

* List post build folder stuff.

* Add android output format as apk.

* Disable package replacement to see if that is the issue location.

* Revert "Disable package replacement to see if that is the issue location."

This reverts commit 31cffe7cb296ccd5796fccccac14edbdbc526452.

* Always try to publish the binlog files.

* Comment out the props file to see if that fixes the AOT error.

* Readd props references.

* Try building without AOT.

* Disable Maui Android Scenarios so that at least iOS on main are being build and measured for SOD.

* Forgot to remove the uploading of the Android APP.

* Disable download attempt of the MauiAndroidApp.

* Reenable full perf run.

* Set the setup branch back to main.

* Undisable MauiScenario.targets file. It semi-causes the AOT issue but should still be enabled for other working builds.

* Add reason for the commented out sections.

[main] Update dependencies from dotnet/arcade dotnet/xharness dotnet/roslyn-analyzers

* Use generic math in System.Numerics.Vectors (#60365)

* Add more use of the Generic Math (#60365)

* Got rid of the dynamic cast (#60365)
Co-authored-by: NTanner Gooding <tagoo@outlook.com>

Preparatory work for fixing the x64 epilog unwind problem for OSR methods.
Changes the jit guid since the PatchpointInfo data structure is altered.

We recently bumped the Android NDK in https://github.com/dotnet/runtime/pull/64567, add a check to CMakeLists-android.txt to validate it.

* Respect generator projects in slngen

We require that the maximum number of prolog instructions all fit in one
instruction group. Recent changes appear to have increased the number of
instructions we are generating the prolog, leading to NOWAY assert on
Release builds and test failure on linux-arm64.

Bump up the number to avoid this problem, and leave some headroom for
possible additional needs.

Fixes #64162, #64793.

* Everithing but ref

* Update ValidateOptions.cs

* Update ref

* ConfigureNamedOptions TDep is notnull

* PostConfigureOptions Tdep is notnull

* OptionsMonitor.OnChange name is notnull

* Revert non-nullable changes

* Fix invalid ref

* Failures notnull only when Failed

* FailureMessage is notnull

* Validation is nonnull

* Update OptionsValidationTests.cs

* OptionsFactory.Create name is nonnull

* Introducing GenTreeDebugOperKind

To track invariants related to opers in asserts
without increasing the size of the primary oper
kind table.

Some shuffling of the oper table to make it look better.

* More "gtlist.h" cleanup

Put all OperIsIdir opers together, fix up formatting,
move opers around to more logical places.

* Remove redundant asserts

* GTK_NOTLIR -> DBK_NOTLIR

There is not a lot of point in this being a "release"
oper kind, as it is really only useful for debug checks.

* GTK_NOCONTAIN -> DBK_NOCONTAIN

* Fix formatting...

There was existing logic to spill but it was there to avoid duplicating costly trees and was
not considering possible interference. Unfortunately, this method is invoked in morph
preorder and child node flags can't be trusted for interference checks.

Fix is to update `fgMakeMultiUse` so it will spill any exposed local.

* Update to StyleCopAnalyzers 1.2.0-beta.406

* Add missing newlines at end of files to satisfy changes to SA1518

* Avoid InitialTarget in libs tree for CoreLib

InitialTargets are quite expensive as they run for every project invocation, even if the target invoked doesn't require the InitialTarget to run. Libraries projects only have one InitialTarget for correctly referencing CoreLib which can be changed so that it runs before RAR.

* Subtract instead of cartesian product in targets

See https://github.com/dotnet/runtime/pull/64000#issuecomment-1030460532. These targets were quite expensive and noticeable in no-op builds. Instead of building the cartesian product via item batching, using subtraction which avoids unnecessary items to be computed.

* Update resolveContract.targets

* Update targetingpacks.targets

* Update resolveContract.targets

* Update resolveContract.targets

The enumerator was missing the last 2 buckets

Fixes #65013

* Update linux build instructions for .NET 6/7
* Add linux musl arm to the list
Co-authored-by: NJuan Hoyos <juan.hoyos@microsoft.com>

Issue: https://github.com/dotnet/runtime/issues/65012

These are no longer being developed/maintained. Thus there is no reason for us to keep running our tests against them.

Also, updating the rest of the DI containers to their latest stable versions.

Fix #64988

* Relax the type check

The type check is too conservative: it prevents partial
definitions from being used in propagation:
```
LCL_FLD V00/1 [X] = { ... }; // Pushed on the stack as a def.

USE LCL_VAR V01 // Has the same VN as V00/1, but the type
                // check prevented it from being replaced.
```
This new version is conservative too, but will do for now
as we don't propagate on (most) partial uses.

Another reason for this change is that in my upcoming refactoring
of copy propagation (that will bring another 0.5% in TP gains), we
will no longer have the "defNode" available.

* Do not propagate shadowed "this"

Ordinarily, shadowed parameters would not be used for
propagation anyway, because of the liveness check, but
"this" bypasses that checks, and so was used, which is
presumably not what we want.

Regardless of that, it is also not profitable to propagate
"this" in such a situation as it extends its live range
and makes the RA unhappy.

* NO_SHADOW_COPY -> BAD_VAR_NUM

* [mobile] Add diagnostics tracing to Android iOS mobile runtime components

* [tests] Reenable eventactivityidcontrol test on Android

Reenables eventactivityidcontrol now that diagnostics_tracing runtime component is included

* [tests] Enable non-eventpipe Android tracing tests to emulate desktop mono

* Revert "[tests] Enable non-eventpipe Android tracing tests to emulate desktop mono"

This reverts commit 3b8ef2356a739ee66962bb65f81db9d8ae64f3f3.

* [tests] Skip JitOptimizationSensitive script on mono

* Update Android GetStandardTransport TcpClient initialization

* [tests] Skip diagnostics tests on browser and Android
Co-authored-by: NMitchell Hwang <mitchell.hwang@microsoft.com>

Co-authored-by: NImran Hameed <imhameed@microsoft.com>

* [wasm] Workaround emscripten bug

Fix https://github.com/dotnet/runtime/issues/64724 and
https://github.com/dotnet/runtime/issues/64725

* Re-enable failing tests

* Revert "Re-enable failing tests"

This reverts commit 52b270d2eef3f48b9b51ed47ea406dbccfe3652b.