.. `xharness`.

Some library tests, like `System.Text.RegularExpressions.Tests` can take more than 15mins.

- Also, fix building `console-v8` sample with `make`

* Use Unsafe.As in ImmutableByteArrayInterop.

Code quality increases.

* Optimize methods in the BlobUtilities class.

* Include more information in exceptions thrown from catch blocks.

* Use spans in BlobContentId, avoiding ImmutableByteArrayInterop.

* Use spans in BlobWriter, reducing pinning and ImmutableArrayInterop.

* Use spans in BlobBuilder, reducing pinning and ImmutableArrayInterop.

* Remove NoInlining from the throw helpers.

It prevents the JIT from looking into the method's body, realizing it's a throw helper, and doing what's best (such as considering it cold).

* Inline `BlobUtilities.Read(Immutable)?Bytes`.

* Avoid a length check introduced by the use of `BinaryPrimitives`.

* Remove `DisallowNull` from `ImmutableArrayInterop.DangerousCreateFromUnderlyingArray`.

* Remove an early bail-out if the buffer was empty.

* Stop using value tuples.

* Fix tests and expose writing a span to BlobWriter.

* Fix stack overflows.

* Shorten BlobUtilities methods that write integers.

* Optimize some methods in `MemoryBlock`.

Fixes https://github.com/dotnet/runtime/issues/76881

* Implement Environment.IsPrivilegedProcess

* Address feedback

* Use one static

* Fix mono wasm

* Address feedback 2

* Address feedback 3

* Fix typo.

* Fix wasm

Let them be valid C# code. Uniform code style as well.

Apply all style auto-fixers on ThunkGenerator

Leverage the new SSA accounting to look for cases of phi-based jump threading
that will not require SSA updates. In particular cases where the phis are all
locally consumed.

Also update documentation on the SSA checker implementation (which aims to
ensure that the SSA accounting we're relying on here is accurate).

Related: https://github.com/dotnet/runtime/pull/71685.

* Dequeue canceled request before making decision for processing queue’s requests

* Update assembly version from hardcoded to MajorVersion

* Bump version to 8 in XsdDataContractExporterTests

* Retrieve major version dynamically for expected message in TypesTest_Negative

* Retrieve major version dynamically for expected message in SurrogateProvider_MemberData

* Manually generate the TestData.resources.
The dotnet exec command generated by the msbuild Target had to be manually executed in the cmdline with the target framework folders for RemoteExecutor hardcoded to net7.0-windows so the resources file could be generated.

* Avoid hardcoded 8 in additional SurrogateTests line

* Fix Diagnostics.EventLog supression message

* Update assembly version from hardcoded to MajorVersion

* Bump version to 8 in XsdDataContractExporterTests

* Retrieve major version dynamically for expected message in TypesTest_Negative

* Retrieve major version dynamically for expected message in SurrogateProvider_MemberData

* Manually generate the TestData.resources.
The dotnet exec command generated by the msbuild Target had to be manually executed in the cmdline with the target framework folders for RemoteExecutor hardcoded to net7.0-windows so the resources file could be generated.

* Avoid hardcoded 8 in additional SurrogateTests line

* Fix Diagnostics.EventLog supression message

* Extract the LocalEchoServer bits from the projects

.. so that the helix bits are in a LocalEchoServer.helix.targets ,
instead of being special-cased in sendtohelix-wasm.targets .
- And this is setup and used by the test projects by importing one file.

* Build the LocalEchoServers specifically without using artifacts .

- The RemoteLoopServer, and NetCoreServer are projects used as aspnetcore
middleware, and loaded by xharness.
- These are built against the live artifacts, same as other projects.
    - But this can be a problem when the libraries in `runtime` are on a
    newer assembly version (say `8.0.0`), but xharness is still built with
    `7.0.0` libraries.
    - In that case, xharness fails to load the middleware:

```
Application startup exception: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.

...

Could not load file or assembly 'System.Runtime, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

   at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
   at System.Reflection.Assembly.GetTypes()
   at Microsoft.DotNet.XHarness.CLI.CommandArguments.TypeFromAssemblyArgument`1.GetLoadedTypes()+MoveNext() in /_/src/Microsoft.DotNet.XHarness.CLI/CommandArguments/Arguments/TypeFromAssemblyArgument.cs:line 29
   at Microsoft.DotNet.XHarness.CLI.Commands.WebServer.<>c__DisplayClass0_0.<Start>b__9(TestWebServerOptions options) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WebServer.cs:line 60
   at Microsoft.Extensions.Options.OptionsFactory`1.Create(String name)
   at Microsoft.Extensions.Options.OptionsCache`1.<>c__3`1.<GetOrAdd>b__3_0(String name, ValueTuple`2 arg)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd[TArg](TKey key, Func`3 valueFactory, TArg factoryArgument)
   at Microsoft.Extensions.Options.OptionsCache`1.GetOrAdd[TArg](String name, Func`3 createOptions, TArg factoryArgument)
   at Microsoft.DotNet.XHarness.CLI.Commands.WebServer.TestWebServerStartup.Configure(IApplicationBuilder app, IOptionsMonitor`1 optionsAccessor) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WebServer.cs:line 126
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)
   at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)
   at Microsoft.AspNetCore.Hosting.WebHost.BuildApplication()
```

- Build the project in isolation from rest of the repo, so that it is
built with references only from the SDK. The built assembly can then be
deployed for use with xharness, just like before.

* add missing files

* [wasm] fixup extensions targets for LocalEchoServer

* [wasm] Use eng/targetingpacks.targets instead of wasm specific targets

* [wasm] Avoid duplicate imports, and don't use the targetingpacks.targets

.. for runtime tests since the paths are set explicitly in the project

* [wasm] Workaround for https://github.com/dotnet/runtime/issues/77707

The middleware projects are now being built separately, so they can
target a different TFM. But when `RunAOTCompilation=true` is set, like
on CI/AOT builds, the build breaks with:

```
To build this project, the following workloads must be installed: macos [/__w/1/s/Build.proj]
To install these workloads, run the following command: dotnet workload restore [/__w/1/s/Build.proj]
```

This is described in https://github.com/dotnet/runtime/issues/77707 .
And the issue is present in `7.0 rc1` also, which is currently used for
building the repo. To workaround it, we unset some properties which
aren't needed anyway for the middleware projects builds.
Co-authored-by: Ncarlossanlop <carlossanlop@users.noreply.github.com>
Co-authored-by: NAnkit Jain <radical@gmail.com>

[main] Update dependencies from 7 repositories

* Add missing type param documentation for Vector64.Create<T>

* Add summaries to the Vector types

* Fix typeparamref

* Address PR feedback

* Update dependencies from https://github.com/dotnet/linker build 20221027.4

Microsoft.NET.ILLink.Tasks
 From Version 7.0.100-1.22525.3 -> To Version 7.0.100-1.22527.4

* Update dependencies from https://github.com/dotnet/linker build 20221031.1

Microsoft.NET.ILLink.Tasks
 From Version 7.0.100-1.22525.3 -> To Version 7.0.100-1.22531.1

* Update dependencies from https://github.com/dotnet/linker build 20221031.2

Microsoft.NET.ILLink.Tasks
 From Version 7.0.100-1.22525.3 -> To Version 7.0.100-1.22531.2

* Update dependencies from https://github.com/dotnet/linker build 20221101.1

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

* Removing empty variable live ranges

The debugger is not using empty variable live ranges.
We are reporting them because they can get extended
later if the variable becomes alive in the immediately
next emitted instruction. If an empty live range is
not getting extended, which we can realize after
emitting all the code or creating a new live range
for the same variable, we can remove it.

* Extending variable live ranges in more cases

When the emitter moved to the next group but has not
emitted any instruction, and the variable died and
becomes alive again, we would like to extend its range.

* Avoiding creating a new debug range when previous is empty

* Updating check for empty debug ranges

* Updating print

* Avoiding printing twice variable live range

* Avoiding reporting empty variable ranges to the vm

* Revert "Avoiding printing twice variable live range"

This reverts commit 4e1cf47dd6cdf9d45ce4a51eaa05b3ec6e4b3b41.

* Revert "Updating print"

This reverts commit 7b79b0d955daa4dc9770b604d6780591b51c9ee1.

* Revert "Updating check for empty debug ranges"

This reverts commit e8b102d489d79028750068decf4f427ad8e5f69f.

* Revert "Avoiding creating a new debug range when previous is empty"

This reverts commit a11fd5d0ffaa98631d731bec1f2619f1d108d33a.

* Revert "Extending variable live ranges in more cases"

This reverts commit 609605a1ca7cf1c0c843dbaf353432ec9ed846e2.

* Revert "Removing empty variable live ranges"

This reverts commit 66d18e031f83c8efe864981b35c0548af49e0714.

* Freeing vm memory when there is no debug info

* Persisting JIT-EE contract on empty debug info

* Update src/coreclr/jit/ee_il_dll.cpp
Co-authored-by: NJakob Botsch Nielsen <Jakob.botsch.nielsen@gmail.com>
Co-authored-by: NBrian Bohe <brianbohe@microsoft.com>
Co-authored-by: NJakob Botsch Nielsen <Jakob.botsch.nielsen@gmail.com>

* Mark and expose additional Vector functions as Intrinsic

* Applying formatting patch

* Ensure Vector64.CreateScalarUnsafe for long/ulong/double is handled

* Ensure we use the right Count

* Ensure small types don't sign extend up to int

* Ensure reflection invocation is correct for Vector<T> bitwise ops

* Adding tests and fixing a couple small typing issues

* Fixing the name of the One property

* Assert GT_RSH for simd isn't TYP_LONG on xarch

* Ensure the correct operation is picked for vector ShiftRightArithmetic

* Fixing StoreAlignedNonTemporal on Arm64

* Add new test ReflectionAddNewMethod

* FIXME: get_param_names, get_marshal_info and custom_attrs need work

* WIP - add a method param reverse lookup

* look up params from added methods

* Remove FIXMEs and unused field

* remove writelines from test

* fix test on coreclr

* why does coreclr have 2 attributes here??

* There should be 2 attributes on the 4th param

* one more place that looks at params

* A couple more places where we look at the Params table

* Check default values on params on added method

* fix lookup if table is empty

* add a gratuitious typeof assert

otherwise the CancellationToken type is trimmed on wasm

* Add a single mono_metadata_get_method_params function

remove duplicated code

Split up "we have a profile" and "we have profile weights" questions.

* Remove Vector128 checks for amd64 APIs

* refactor emit_sum_vector (amd64)

* [mono][wasm] Handle delegates decorated with [UnmanagedFunctionPointer] in
the interp-to-native generator.

Fixes https://github.com/dotnet/runtime/issues/76930.

* Update src/tasks/WasmAppBuilder/PInvokeTableGenerator.cs
Co-authored-by: NAnkit Jain <radical@gmail.com>

* Update src/tasks/WasmAppBuilder/PInvokeTableGenerator.cs
Co-authored-by: NAnkit Jain <radical@gmail.com>

* Update src/tasks/WasmAppBuilder/PInvokeTableGenerator.cs
Co-authored-by: NAnkit Jain <radical@gmail.com>
Co-authored-by: NAnkit Jain <radical@gmail.com>

* Add option for truncated stream detection

fix https://github.com/dotnet/runtime/issues/47563

* Use RemoteExecutor

move the test to concrete classes as abstracted classes are not supported by RemoteExecutor

* review feedback

* use same error text message

* cache appcontext getswitch

* fix failing test

* slice byte array for assertion

* renaming

* add missing RemoteExecutor.IsSupported

* fast check first

This reverts commit 0e24ea7c.

It broke all the perf pipeline wasm builds. It happens with v8 `10.9.130`:

```
Error: Invalid 'startMark' argument: No numeric 'startTime' field
    at pe (/home/helixbot/work/B2E7090F/w/A520093B/e/performance/artifacts/bin/for-running/MicroBenchmarks/659adab0-5c86-4e74-8913-672bd56fd58e/bin/net7.0/browser-wasm/AppBundle/dotnet.js:3:12994)
    at /home/helixbot/work/B2E7090F/w/A520093B/e/performance/artifacts/bin/for-running/MicroBenchmarks/659adab0-5c86-4e74-8913-672bd56fd58e/bin/net7.0/browser-wasm/AppBundle/dotnet.js:5:95874
exiting due to exception: Error: Invalid 'startMark' argument: No numeric 'startTime' field
```

- It works fine with older versions like `10.7.193` (current stable).
- It wasn't caught in the CI checks because those are using an older version of v8.

Allow up to 1/50 variance between the expected and computed values.

Fixes #77450.

* Move docker tags to -latest

As part of https://github.com/dotnet/arcade/issues/10123, we have added a floating -latest tag to all currently in-support docker container images. This change moves all container reference to the -latest version so runtime can get all of the latest updates to the containers.

* Change all of the centos-8-rpmpkg images to centos-7-rpmpkg

CentOS 8 was EOL and has been removed as a supported docker image in dotnet-buildtools-prereqs-docker

* Replace -latest tags with new tag schema

* Move tests off eol docker containers

* Update the images in the new infra

Co-authored-by: NBrian Bohe <brianbohe@microsoft.com>

* Expand ComWrappers mask for vtable lookup on 64-bit

* wip

* wip

* cleanup

* feedback

* feedback

* Update SuperPMI artifact logging

- Add
  `[assembly:System.Runtime.Versioning.SupportedOSPlatform("browser")]`
  to the browser, and console templates. This would allow the analyzers,
  if enabled, to treat the assembly as one that will run only on
  browser.

- Populate `@(SupportedPlatform)` with only `browser`, for *wasm*
  projects, similar to https://github.com/dotnet/sdk/blob/fef8cedfb6b4ac85a7e135f3e4f155e29cdcbdf1/src/BlazorWasmSdk/Targets/Microsoft.NET.Sdk.BlazorWebAssembly.5_0.targets#L75-L79

- This also fixes the firefox CI build which regressed recently