I have noticed that these two tests are still conditionally
executed on x64 only. I don't see why they shouldn't work on
other architectures.

Thanks

Tomas

* Reuse SDK target for latest commit hash
Co-authored-by: NViktor Hofer <viktor.hofer@microsoft.com>

* Further clean-up corehost.proj
Co-authored-by: NViktor Hofer <viktor.hofer@microsoft.com>

* Add assembly name to SuperPMI collection

For each class, add JIT/EE calls to getAssemblyName so the SuperPMI
collections contain this information. This can be useful to try and track
down where a particular function in a large method context hive came
from.

Only do this when `COMPlus_EnableExtraSuperPmiQueries=1` is set.

* Formatting

Enable Hot Reload API on Linux

Only define EnC_SUPPORTED for vm/ee on xplat. Doesn't enable the ENC ICorDebug API.

Enable hotreload api tests on Linux/MacOS. API not implemented on arm/arm64

Remove all the ENC_DELTA_HACK code. Remove more ENC_DELTA_HACK code from ilasm

policy was always set to MONO_UNHANDLED_POLICY_CURRENT.  The
legacy (pre-.NET 2.0) policy was not used.

This method costs trees, which can in turn modify the IR by swapping operands.
As a result the bool value returned doesn't properly reflect whether any
changes happened.

This impacts proper reporting phase status by `optOptimizeLayout'. Since phase
status just gates post-phase dumps and checks, we'll just claim this phase
always modifies IR.

Add similar workaround for `optInvertLoops`.

Fixes #48494.
Fixes #48495. 

* Update hardcoded rids for targeting/runtime pks

* building single file host with clr partition

* make coreclr_static a STATIC lib again

* [mono] Implement public hot reload API

Also add ApplyUpdateSdb that takes byte[] arguments for use with
mono/debugger-libs as its awkward to call a ROS<byte> method from the debugger.

Contributes to https://github.com/dotnet/runtime/issues/45689

* Update src/mono/System.Private.CoreLib/src/System/Reflection/Metadata/AssemblyExtensions.cs
Co-authored-by: NMarek Safar <marek.safar@gmail.com>

* Don't allow changes to System.Private.CoreLib

* formatting

* more formatting

* Add a TODO to remove ApplyUpdateSdb

* update DeltaHelper

* don't use ApplyUpdateSdb in DeltaHelper

* throw InvalidOpertionException for corlib changes with hot reload disabled

* Run the test on mono on all platoforms; CoreCLR windows only

* Use resource string

* Address review feedback
Co-authored-by: NMarek Safar <marek.safar@gmail.com>

* Don't use container for WASM

* Remove dashes

* Remove comments for testing

Rather than using a StringBuilder in both ToString and TryFormat, we can just write ToString in terms of TryFormat and use stack space for the small string being generated.  As part of this, I removed the extra code optimizing ToString(0) and ToString(1), as I can't find any real code anywhere that does that and it's not worth the extra lines.

* Starting to add IsInvariant helper

* Finished IsInvariant helper. Starting testing

* Removed IsInvariant from GenTree to avoid asserts

* Formatting

* Fixed missing not operator

* Changed AsOp() call to 'this' to avoid failing assertions

* Formatting

* Update src/coreclr/jit/morph.cpp
Co-authored-by: NSergey Andreenko <seandree@microsoft.com>

* Update src/coreclr/jit/compiler.h
Co-authored-by: NSergey Andreenko <seandree@microsoft.com>

* Apply suggestions from code review
Co-authored-by: NSergey Andreenko <seandree@microsoft.com>

* Change arguments to const to avoid cast

* Formatting

* delete `IsInvariant` from Compiler.
Co-authored-by: NSergey Andreenko <seandree@microsoft.com>

* Annotate framework assemblies as trimmable

This will opt them into trimming with the behavior described at https://github.com/mono/linker/blob/main/docs/design/trimmed-assemblies.md#assemblymetadataistrimmable-true.

* Add a condition to let projects opt out

A project just needs to set <SetIsTrimmable>false</SetIsTrimmable>, and
it won't get the trimmable metadata.

I also got rid of the SkipFrameworkAssemblyMetadata check since I don't
think the IsTrimmable metadata should be tied to whether we are building
a framework assembly, and this property was unused as far as I could tell.

* do not expect a single receive

* use expected.Length

* enable test

* Remove trimming attributes from any assembly.

These attributes are allowed to be in any assembly, for assemblies that are built using older TFMs where the attributes didn't exist.

Fix #48399

* Remove nullable attributes as well.

Co-authored-by: NNathan Ricci <naricc@xam-emag-01.redmond.corp.microsoft.com>

[master] Update dependencies from dotnet/xharness

* make comparer field readonly

* abstract IComparer in PriorityQueue generic tests

does minor refactorings and adds new tests

* add PriorityQueue property tests

* address feedback

* add seed for deterministic runs

* apply var fixes in property tests

* replace FsCheck properties with theories

In past I was involved in mono/debugger-agent.c, but not anymore, hence removing myself from CODEOWNERS file

* [interp] Fix overflow in PROFILE_INTERP log

* [interp] Replace LDFLDA of offset 0 field with MOV

Commonly used when accessing first field of valuetypes, eg span operations. Will help with cprop and remove redundant instruction.

* [interp] Remove redundant opcode

[master] Update dependencies from mono/linker

* Remove the MonoClassRuntimeInfo structure, store the runtime vtable directly in MonoClass.

* Remove the 'domain' argument from mono_class_vtable_checked ().

* Remove the 'domain' argument from the object allocation functions.

* Remove the 'domain' argument from the m_.._alloc methods.

* Revert accidental changes.

* Remove more unused 'domain' parameters.

* Remove more remoting code.

* Remove shared code support.

* Remove the 'domain' argument from the IMT builder functions.

* Remove the 'domain' argument from the m_method_ functions.

* Remove more domain usage from the JIT backends.

* Remove the MONO_ARCH_HAVE_PATCH_CODE_NEW ifdef, all architectures support it now.

* Remove 'domain' argument from mini_jit_info_table_find ().

* Remove 'domain' argument from mono_arch_unwind_frame ().

* Remove unused/unfinished AOT cache code.

* Remove the 'domain' argument from mono_resolve_patch_target ().

* Remove domains from the stack walk/exception handling code.

* Remove domains from mono-debug.c.

The memory in mono-debug.c is now owned by a MonoMemoryManager instead of by a domain.

* Remove unused mono-mlist.{h,c}.

* Fix the coverage profiler build.

* Fix the build.

* [wasm] pack: Let the workload configure the runtime pack path

* [wasm] update webassembly pack description

* [wasm] Makefile: fix being able to `make build`

* [wasm] Fix AOT compilation to work before publish

Instead of using runtime pack, and other assemblies from the
publish folder, we are now using them directly from the source
location. This means that `System.Private.CoreLib` can be in a different
directory, than the assembly being precompiled.

So, we need to set `MONO_PATH` to the relevant paths that will have the assemblies.

This manifests during blazor workload based builds.

* [wasm][aot] Don't strip the source assemblies in place

Currently we run `mono-cil-strip` on assemblies, in the AOT case, but we
do that in-place.

This is problematic because the assemblies from the runtime pack will
get modified in their original location (nuget/etc), since we don't use
them from the publish folder anymore.

- This would mean that a subsequent attempt to build with AOT would fail
  because now the original assemblies are already stripped!

- this also becomes apparent if you have the runtime pack installed in a
  system dotnet folder, eg. as a pack - `/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.browser-wasm/`,
  because a regular user wouldn't have permissions to modify that.

Solution: Write the stripped assemblies into the obj dir

* [wasm] Make the final list of wasm assemblies as an item

- Blazor skips the generation of the app bundle when running
 `WasmBuildApp` target.
- Because of the previous commit, the locations for the final assemblies
  could be different (when aot+stripping), which needs to be surfaced
  for blazor. So, generate a `@(WasmAssembliesFinal)` item for that.

* [wasm] Allow enabling assert messages with $(MonoEnableAssertMessages)

* [wasm][aot] WasmApp.targets: check that we have .bc file for each assembly

Just a sanity check to ensure that due to some build authoring error, we
are not building dotnet.js/wasm with no .bc files! That just shows up as
an assert:

`* Assertion at /Users/radical/dev/r3/src/mono/mono/mini/aot-runtime.c:2651, condition `<disabled>' not met`

.. which is:
    `g_assert (info->version == MONO_AOT_FILE_VERSION);`

..  `0 != MONO_AOT_FILE_VERSION`

* [wasm] remove UsingTask for non-exitant WasmAOT

* MonoCrossAot pkg: use mono-aot-cross.exe on windows

* [wasm] Fix up emscripten command invocations for windows

* [wasm] WasmApp.targets: move some property inits closer to their use

* [wasm] fix build for browser-profile sample

* [wasm] fix emcc invocation for getting the version

* [wasm] Add new RunWithEmSdkEnv task

* [wasm] Use `RunWithEmSdkEnv` to run `emcc` commands

* [wasm] AotCompiler: use platform specific path separator

* [wasm] RunWithEmSdkEnv: quote path on windows

* [wasm] Use new ReadEmccVersion to get the versions

This simplifies the target too, and works on windows.

* Update src/installer/pkg/sfx/Microsoft.NETCore.App/Microsoft.NETCore.App.MonoCrossAOT.Sdk.props
Co-authored-by: NPranav K <prkrishn@hotmail.com>

* fix messageimportance for debug msg

* Fix emcc invocation on windows, thanks to @pranavkm

* Don't strip assemblies with mono-cil-strip for aotinterp mode

* [wasm] Remove ReadEmccVersion task, and use msbuild to get the version

.. string instead. We do this by looking for the line with `'emcc'` in
it, since the other lines are the license text. Hopefully, this isn't
too brittle, since we are invoking `emcc --version`.

* Fix emcc version extraction to not depend on a specific string
Co-authored-by: NPranav K <prkrishn@hotmail.com>

Do not emit Avx2 instruction `vpcmpeqd ymmReg, ymmReg, ymmReg` for `Vector256<T>.AllBitsSet` intrinsic when Avx2 is not supported (#48383)

Emit `vcmptrueps ymmReg, ymmReg, ymmReg` instead

On Linux, libnuma.so{.1} are symlinks to libnuma.so.1.0.0.

When installed from default package manager; Ubuntu (libnuma-dev) and
Alpine (numactl-dev), found these two symlinks:
`{libnuma.so,libnuma.so.1} -> libnuma.so.1.0.0`

On Fedora (numactl-libs):
`libnuma.so.1 -> libnuma.so.1.0.0`
(there is no version-less variant)

PR adjusts probing fallback flow based on this info.

The old certificate chain used a root certificate that is deprecated
and is starting to disappear from some trust stores. The removal of
the root certificate led to a few failing tests, and other tests not
running since they were conditional on the trust of that certificate.

* WIP

* Add Alpine specific steps

* Fix musl string

* Fix musl string

* Add comment block

* Update Helix precommand for Alpine

* Add container support for Perf leg

* Remove dupe container

* Add apk installs

* Add libgdiplus

* Fix typo and remove --force-install from pip command

* Remove --force-reinstall from Alpine job

* Add pip upgrade step

* Add cargo install

* Add back full runs

* Remove PR line

* Remove temp files

* Fix spacing issue

* Resolve ILLink warnings in System.Linq.Queryable

Contributes to #45623

* Respond to PR feedback.

Annotate public AsQueryable() method as RequiresUnreferencedCode.

Add hot reload apply changes API: AssemblyExtensions.ApplyUpdate

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

Currently Windows only. Fail hot reload API if debugging.

Added some simple invalid parameter testing to the new ApplyUpdate API. 

* Fix AV in NativeRuntimeEventSource QCalls

* Add test

* Use WriteEventCore APIs to emit events on Mono

* Separate out Mono/CoreCLR implementations to different files

* Fix wasm build