* Use JitStdOutFile for .dasm creation

* add back logging.debug

Throw if we ever take the fall thru on a conditional branch at the end
of a method.

Related to https://github.com/dotnet/runtime/issues/73474 but doesn't
fix it: this just makes the interpreter throw instead of falling off
the end of the transformed CFG

Fixes the mono "HelloWorld" sample (src/mono/samples/HelloWorld) on
desktop platforms

## 1. Fix random HotReload test failures
Some of the hot reload tests fail randomly because they call the updated methods too early.
The tests used `Thread.Sleep(3000)` to wait for the method to get updated, and the proxy
to respond to that. And that's essentially racy.

Instead, wait for the `breakpointResolved` event, or the `scriptParsed` events for the methods,
as appropriate.

Fixes https://github.com/dotnet/runtime/issues/66024
Fixes https://github.com/dotnet/runtime/issues/72946 

## 2. Fix race in adding/removing event handlers

Use ConcurrentDictionary for event listeners, and notification handlers, since they can be modified
from different threads.

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

## 3. Fix a race condition where the tests start calling methods before the app is ready

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

* WIP: fix overflow checking

* Change limit to 9 digits

* Fixed the same bug in other places

* Remove mistake include

* Move expensive tests to OuterLoop

We were not checking the result of the ExecutableAllocator::Commit call
for mapping the RW page in the case of interleaved heaps. I've seen a
failure in the CI that seems to be caused by this - when we succeeded
committing the RX page, but failed to commit the related RW page, we
have then crashed when trying to initialize the precode stubs data.

This change adds the check to fix the problem. This causes the
LoaderHeap allocation to fail as expected in such case.

* PNSE for domain sockets on iOS/tvOS
* Re-enable some tests which SHOULD now throw PNSE

* Add lowering support for conditional nodes

* Contain conditionals

* Fix formatting

* Use AND and CMP nodes

* Fix formatting

* Remove LowerNodeCC changes

Change-Id: Icdf1828905c4a3f210b06e047ef3c0ac913d71f7
CustomizedGitHooks: yes

* Remove asserts & fix variable names

* Better contain checks for conditional compares

* Simpler contained conditions codegen

* Remove Conditional Compare nodes

* Minor cleanups

* Generate AND compare chains

* Fix unsigned compares && reduce chain check recursion

* Add compare chain tests

* Review fixes

* Use GenCondition

* Change CompareChainSize to IsValidCompareChain

* Move lowering functions to lowerarmarch

* Formatting fixes

* Fix SELECT issues

* Fix test output messages.

* Better explanations for AND chains

* Compare chains should not contain tst compares

Change-Id: I8a1761e1e89f589e1daf0318e120aae5dd3d7241
CustomizedGitHooks: yes

* Don't allow tst compares in codegeneration of compare chains

* Add tests for chains with tst compares

* Don't allow tst compares in lsrabuild of compare chains

## Issue

Currently, whenever a darc flow PR is opened, we cannot trigger different jobs based on which
dependency got updated. This is needed because in some cases, like for ILLinker, Emscripten
updates we want to trigger all the wasm jobs. But that might not be needed for some of the other
dependencies.

- This causes failures to slip through to `main`, which gets discovered after the fact as other PR
failures, or rolling build failures, creating extra work for developers.

## Solution

- This PR identifies the changed dependencies, and emits one azure variable per dependency,
which can then be used in conditions in the yml .
- The changed dependency can be checked as `dependencies.evaluate_paths.outputs['DarcDependenciesChanged.System_CommandLine']`

- Included this in the `evaluate_paths` job itself, instead of creating another job

- Also, use this for wasm jobs

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

* Improved server logging to include S.N.Quic traces as well.

* MsQuicBuffers copy given memory into native instead of pinning

This reverts commit 9865cc7a.
We believe the problematic change has been reverted so the test can be re-enabled.

- move asset related logic to separate file`assets.ts`
- split logging code into separate file `logging.ts`
- add `dotnet.wasm` and `dotnet-crypto-worker.js` to mono-config.json
- moved `readSymbolMapFile()` call to `startup.ts`
- fixed bug in `setup_proxy_console()` which didn't really copy the original `log` and `error` functions of the console and caused recursion on error.
- moved `init_crypto` after `mono_wasm_load_config` in `mono_wasm_pre_init_essential_async`
- added new resource type `js-module-crypto` and `js-module-threads`
- changed the detection of blazor startup sequence to not be disabled by presence of config, but only by config.assets having some assembly in it.
Co-authored-by: NMarek Fišera <mara@neptuo.com>

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

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

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

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

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

Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22403.1 -> To Version 7.0.0-beta.22408.3
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Condition ExternalConsoleManipulation_RegistrationRemoved_UnregisterSucceeds on RemoteExecutor.IsSupported (#73603)

so that accessing the result address throws exception.

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

* Add handling of generic attributes to CustomAttributeDecoder

If the attribute constructor refers to the generic T in its signature, we would throw `BadImageFormatException`. This adds handling by capturing the generic context and interpreting the signature variables when needed.

* Add tests
Co-authored-by: NMichal Strehovský <MichalStrehovsky@users.noreply.github.com>

This adds prefetching to the mark phase.

The idea is that once we have established that an object is in one of the generations we want to collect, we prefetch its memory before we determine whether we have marked it already. This is because the mark bit is in the object itself, and thus requires accessing the object's memory.

As the prefetching will take some time to take effect, we park the object in a queue (see type mark_queue_t below). We then retrieve an older object from the queue, and test whether it has been marked. This should be faster, because we have issued a prefetch for this older object's memory a while back.

In quite a few places we now need to drain the queue to ensure correctness - see calls to drain_mark_queue().

[PERF] Fix "x$PERF_PREREQS_INSTALLED was unexpected at this time" Error for Microbenchmarks (#73584)

* Try double brackets.

* Only use the bash check if running on non-windows machine, added command for running on windows machines.

* Undoing changes to if statement brackets (double to single now) as the double bracket is not necessary.

* Use the correct, previously removed command.

* Disable useless warnings
- Detect use of dynamic modules in PGO data processing and skip them instead of generating useless, non-actionable warnings
- Infrastructure currently used only for dynamic modules, but could be extended in the future to provide a means to ignore assemblies based on the set of assemblies specified on the commandline.

Fixes #68000

* Update src/coreclr/tools/dotnet-pgo/Program.cs
Co-authored-by: NMichał Petryka <35800402+MichalPetryka@users.noreply.github.com>
Co-authored-by: NMichał Petryka <35800402+MichalPetryka@users.noreply.github.com>

* Enable test only when LLVM is enabled

* Add back SIMD intrinsics support for X86Base.Pause

* Disable test for llvm

We were only handling uses of promoted locals when varTypeIsStruct(lcl)
was true. For TYP_LONG promoted locals on x86 it is not.

Fix #73559

* [wasm-ep] remove in-JS VFS tracing support

use the websocket diagnostic server support instead

* remove browser-mt-eventpipe sample

use the browser-threading sample for working with threading
use the browser-eventpipe sample for working with tracing

* remove the EventPipeSessionOptions, too

* Set up HttpClient for ClientWebSocket.ConnectAsync

* more tests

* Update src/libraries/System.Net.WebSockets.Client/src/System/Net/WebSockets/WebSocketHandle.Managed.cs
Co-authored-by: NMiha Zupan <mihazupan.zupan1@gmail.com>

* Apply suggestions from code review
Co-authored-by: NMiha Zupan <mihazupan.zupan1@gmail.com>

* Refactoring websockets test inheritance
Co-authored-by: NMiha Zupan <mihazupan.zupan1@gmail.com>

This introduces a lookup table for regions where we can find the current generation, the planned generation and a couple flags efficiently, i.e. by simple indexing into table.

The table has byte-sized elements where the low 2 bits represent the current generation and the high 2 bits represent the planned generation. The 4 bits in between are available for flags, 2 are used so far, one to show that a region was swept in the plan phase, and one to show that a region was demoted.

The table is used in the mark phase, in the mark_through_cards_helper (which is also called in the relocate_phase), and in the write barriers (for now only the most frequently used ones, Array.Copy has its own way of setting cards that I haven't fixed).

I have changed the write barrier to only set single bits for the case where a pointer to younger generation is stored into an object in an older generation. This costs an interlocked operation in the case the bit is not already set. In the test cases we looked at this is more than compensated by lower cost in card marking. For cases where the cost of the interlocked instruction is too high, an escape hatch has been provided the form of the COMPLUS_GCWriteBarrier setting which can be used to select another flavor of write barrier - either a more precise write barrier for regions, or an imprecise write barrier. Both set whole bytes and thus need no interlocked operations.

The write barrier uses a global ephemeral range to decide quickly whether a stored pointer can be in an ephemeral generation at all. For now, this global ephemeral range is simply set to the address range of the whole heap, to avoid having to update the write barrier on the fly. A slightly more sophisticated approach that takes into account low gen 2 regions is present in the code, but disabled for now.

* Avoid additional Pipes invocation and clean-up project

* Update System.IO.Pipes.AccessControl.csproj

* Replace MissingInteropDataException with NotSupportedException
* Replace MissingRuntimeArtifactException with MissingMetadataException (it was already used as a MME in some spots anyway). I'll try to get rid of MME later.
* Change the messages to refer to static analysis as the fix, not RD.XML.

* Fix of VHO for most test cases.

* Cleanup.

* New testcases with auto-props.

* Adjusted ProtectionLvlTest to new changes.

We no longer root all assemblies by default and we don't need to advertise the size switches to much. Also, we need to establish what switches we actually want to support (document on docs.microsoft.com) for real.

* Refactor input bubble checks to work in non-composite scenarios
- Input bubble checks for making sure that the input bubble is valid are not currently processed for non-composite scenarios
- Refactor them so that they are not n^2 in cost, and are handled for both composite and non-composite scenarios