* Use "read" to fetch misaligned 64bit values

* remove read_direct

* rename read() -> read_byte()

#63496)

Co-authored-by: qiaopengcheng <qiaopengcheng-hf@loongson.cn>
Co-authored-by: Jan Kotas <jkotas@microsoft.com>

Co-authored-by: kasperk81 <83082615+kasperk81@users.noreply.github.com>

* Clarify P/Invoke shims guidance for OOB assemblies

The discussion in PR #63421 clarified that System.Native shims for UNIX
APIs aren't appropriate for assemblies that don't ship as part of the
Microsoft.NETCore.App framework.

Updating the interop guidelines to capture that clarification.

* Update docs/coding-guidelines/interop-guidelines.md

Co-authored-by: Stephen Toub <stoub@microsoft.com>

Co-authored-by: Stephen Toub <stoub@microsoft.com>

`init-vs-env.cmd` is going to set up the environment for x86 tools (the "VS Developer Command Prompt") and that messes with things if they run before we run vcvarsall to set the actual target architecture, so it's better not to have such window. We might not even run the vcvarsall line if native test build is skipped.

As an additional improvement, init-vs-env.cmd can also run vcvarsall and set up CMake, so I'm asking it to do it (done by passing an extra parameter to the script to specify which environment to activate).

I need this change for a subsequent change that is broken if we have x86 tools set up.

(1) Reduce contention on the pool lock. This is done mainly by (a) not calling TrySetResult on the queued waiter under the lock -- instead, do this outside the lock and retry as necessary for canceled requests; (b) avoid doing diagnostic logging under the lock.
(2) Improve handling of failed connection attempts so we don't fail requests unnecessarily.

* Fix NETStandard library using JSON source gen

NETStandard libraries using JSON source gen would fail to load on
.NETCore due to missing IsExternalInit in the assembly.

On .NETCore this is defined, whereas on .NETStandard JSON carries an
internal copy.  The compiler emits references to the internal type when
a NETStandard library calls init-only setters in JSON types, but these
references are not satisfied when the library runs on .NETCore.

Fix this by adding a type forward to JSON for the IsExternalInit type.

* Address feedback

* Update src/libraries/System.Text.Json/tests/System.Text.Json.SourceGeneration.Tests/NETStandardContextTests.cs

Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com>

Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com>

This is a stopgap measure to make merged test logs easier to read.
Jeremy considers a broader cleanup of the test wrapper generator
that may ultimately supersede or replace this change.

Thanks

Tomas

)

* Fix exception propagation over HW exception frame on macOS arm64

There is a bug in setting up the fake stack frame for
the PAL_DispatchExceptionWrapper. The FP and SP were not saved
to the stack frame and the FP of the context was not set to
match the fake prologue. That caused failure to unwind over the
PAL_DispatchExceptionWrapper, reaching an unrelated native
function.

This change fixes it.

* Add regression tests for the issue

* Real fix of the issue

Unifies the hardware exception frame unwinding with Linux,
it is necessary on arm64 to get correct and distinct LR and
PC in the frame of the hardware exception.

* Fix translation of Ping error codes

* Modify SendPingToExternalHostWithLowTtlTest

* Usage of TtlReassemblyTimeExceeded

* Revert "Usage of TtlReassemblyTimeExceeded"

This reverts commit 9194df0.

* Eliminate branch and fall-back to default

* Style change: Usage of switch expressions

* Style change : Usage of switch expressions

* Revert "Modify SendPingToExternalHostWithLowTtlTest"

This reverts commit fd76e9d.

1. Instead of hardcoding specific command lines for wasm samples in `sendtohelixhelp.proj`, generate a run script, which allows moving the execution commands to the respective projects.
2. this enables running the library tests additionally for v8, and browser, in case of `runtime-manual`. This was recently changed to run only for nodejs
3. And avoids running samples on debugger tests build