Forthcoming edge-based instrumentation will need to handle some BBF_INTERNAL
blocks, so update main processing logic to accomodate this.

Also have `fgInstrument` return proper phase status, so we get after-phase
dumping if any instrumentation is added.

During my last PR about icordebug I included this error, fixing it.
Co-authored-by: Nthaystg <thaystg@users.noreply.github.com>

They were nearly identical already, move them to a common location.

* Add NotNullWhen(true) on Directory/File.Exists.

* Apply suggestions.

* Improve msg for missing libicu

* add comment

* add aka.ms

* better link

Same as https://github.com/dotnet/runtime/pull/47417

Cause a connection abort when HTTP/2-only frame and settings types are received in HTTP/3. (Progress toward HTTP/3 draft 31 compat) (#43287)

Send h3-29 through h3-31 for ALPN as we are compatible with all of them.
Move some of the loopback test code into the stream class rather than connection class.
Add a basic test for SETTINGS frame receipt.
Fix some tests that were explicitly using Http3LoopbackServer and did not see the new "Mock" QUIC setting introduced in https://github.com/dotnet/runtime/pull/43076

* Randomize SNI

* remove debug message

* Fix the http test

* Add explanation comment

* Remove accidental indentation

debugger-protocol.h was missing from the tarball
Co-authored-by: Nakoeplinger <akoeplinger@users.noreply.github.com>

[wasm] Add ability to link out unused icalls by setting the WasmLinkIcalls msbuild property. (#44236)

* [wasm] Add ability to link out unused icalls by setting the WasmLinkIcalls msbuild property.

* Address review comments.

When SIGSEGV is not handled by .NET runtime (e.g. when it occurs in code
out of its control), the SIGSEGV handler ends up calling
DiagnosticServer::Shutdown in the runtime via a registered shutdown callback.
That method ends up calling Thread::GetFrame, which asserts if the
current SP is out of a valid range for the regular stack. The problem is
that SIGSEGV handler is called on an alternate stack and so this
callback ends up being called on that stack too. That causes this
assertion to fail, because the current thread is not marked as executing
on alternate stack, which would skip that assert.

This change fixes it by passing through a bool flag indicating whether
the callback was called on an alternate stack or not. And in that
callback, we set the flag on the thread accordingly.

Instead of failing to compile methods with filter clauses, make them
enter the interpreter.
Co-authored-by: Nvargaz <vargaz@users.noreply.github.com>

Co-authored-by: Nvargaz <vargaz@users.noreply.github.com>

* Add Mono EventPipe rundown support.

Add support into Mono VM emitting rundown events into EventPipe stream.
All rundown events emitted by CoreClr during EventPipe rundown phase
are now also emitted by Mono, making sure enough meta information
is available for tooling to correctly resolve callstacks (not yet emitted)
included in EventPipe events emitted by Mono VM.

If an exception is throwed in IpcTraceTest::Validate readerTask before
it signals sentinelEventReceived, test will hang on:

sentinelEventReceived.WaitOne();

When hitting this case the error is hard to spot and looks like a
hanging IPC client, but when looking at it from the runtime side
you get a correct close of IPC channel and termination of streaming
thread.

I have hit this in a scenario where we hit an exception deep within
EventPipeEventSource constructor, in that case due to a runtime issue
loading a library on Windows, but since the exception is not rethrown
from the task, no error is seen on client side, the test will just hang
forever.

With this fix, the test will wait on either the sentinelEventReceived
or readerTask and if readerTask get signaled due to an exception,
it will be re-throwed all the way up to RunAndValidateEventCounts
printing test failure and exception info into the log, simplify the
debugging of these kind of failures a lot.

GetFullyQualifiedName returns special strings for modules without
paths. Those names are currently localized. To improve predictability,
this change removes localization for these strings.

* Make the GetAppDomainStaticAddress test more stable

* fix lock issues in profiler tests

* Code review feedback
Co-authored-by: NDavid Mason <davmason@microsoft.com>

Contributes to #45623

Refactor `fgInstrument` and related methods and classes, so that the strategies
for block and class instrumentation are clearly separated out, and can be
varied.

* [interp] Add basic blocks in reverse order, then reverse

g_list_append has to repeatedly traverse the list using g_list_last to
find the last element.

Instead use g_list_prepend to add the new bb to the front of the list
and then reverse at the end (g_list_reverse is inplace and doesn't allocate)

* [interp] Don't generate basic_blocks list if not generating seq points

Still fill in offset_to_bb, but don't make a list unless needed.

* Activity Status support

* Apply the agreed on behavior

* Implemented AdvSimd Abs intrinsic on arm64

`superpmi.py collect` has a new `--crossgen2` option that specifies
to run crossgen2 on all the assemblies specified with the
`-assemblies` option.

For example:
```
py c:\rt\src\coreclr\scripts\superpmi.py collect --crossgen2 -output_mch_path c:\win-x64-cg2.mch -assemblies c:\rt\artifacts\tests\coreclr\windows.x64.Checked\Tests\Core_Root\System.Private.CoreLib.dll
```

There are currently quite a few failures during the replay
"cleaning" phase with a System.Private.CoreLib collection:
5654 compilation failures out of 14705 functions, including 100
JIT asserts.

In contrast, the crossgen(1) collection has 3 failures out
of 20165 functions.

So, there is some work to be done to make SuperPMI collection
of crossgen2 compilations work well.

The change in spmirecordhelper.h is to work around what appears to
be a crossgen2 bug: when the JIT calls `getCallInfo`, sometimes crossgen2
sets sig.sigInst.methInstCount in the result CORINFO_CALL_INFO to non-zero,
but it sets sig.sigInst.methInst to `nullptr`, which should be illegal:
the count indicates how many elements are in the array, so you can?t have a
null array with a non-zero count. Maybe the JIT doesn?t look at these fields in this
scenario for some reason, but SPMI tries to serialize/de-serialize the array,
and was crashing.

Fixes #45909

Refactor tests in SendFile.cs to utilize SocketTestHelper<T>
As a result cover some cases which were uncovered before (for example Dispose VS async).
Add more checks and tests as discussed in #47230.

The _password field is not needed since CryptDeriveKey was not ported
from the Desktop framework.

Removing the field also allows removing a defensive copy and clearing it
during disposal.

* BigInteger changes

* sq

* Runtime side unit tests

* Half tests

* Address feedback

* sq

* Move to a ThrowHelper class

* Move to invariant number format

* Move to canonical throw

* sq

* sq

* Fix bad unicode char

* Add the percent tests back

This checkin adapts the mark list logic for regions.

The basic idea is that as plan_phase goes through the regions, it calls get_region_mark_list obtain the mark list for each region.

How get_region_mark_list works is different for WKS and SVR flavors of the GC:

 - for WKS, we have a single sorted mark list. Finding the mark list section corresponding to a region is done via binary search in the mark list.

 - for SVR, each GC thread, after sorting the mark list, determines where the sections corresponding to all the regions start and end. This is stored in tables mark_list_piece_start and mark_list_piece_end which are now indexed by region number. Later, get_region_mark_list merges the pieces for a region from all heaps. This is very similar to what merge_mark_lists did before.

Add new Task-based UDP socket methods and reimplement existing ones using SocketAsyncEventArgs (#47229)

Closes #41502, but does not change the existing APM methods

Microsoft.NET.ILLink.Tasks
 From Version 6.0.0-alpha.1.21075.2 -> To Version 6.0.0-alpha.1.21076.1
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

* test WindowsIdentityImpersonatedTests runs

* fix win8

* add test variant

* final cleanup

Funnel PGO instrumentation data from runtime to crossgen2

- Representation of instrumentation data within crossgen2 and dotnet-pgo
- New uncompressed mibc format for easier debugging/faster processing
- Storage of instrumentation data in mibc file
- Parser for instrumentation data to load from mibc file
- Translation of crossgen2 in memory representation of instrumentation data from managed form to jit

Future PGO work will include
- Instrumentation data storage and extraction from R2R files
- Move Pgo type handle histogram processing into JIT (which will make type guessing work in crossgen2 as well as in the runtime)
- Triggers for controlling Pgo data extraction
- Size control for pgo instrumentation data

• Avoid double-writing of crossgen2\clrjit_win_x64_x64.dll file.
• Avoid extra slashes in paths.