* When we don't have pdb we still can get some information about the methods like attributes (public, private, protected, etc) which are used for a better debugger experience.

* Update src/mono/wasm/debugger/tests/debugger-test-with-pdb-deleted/debugger-test-with-pdb-deleted.csproj
Co-authored-by: NAnkit Jain <radical@gmail.com>
Co-authored-by: NAnkit Jain <radical@gmail.com>

Around GC static bases placed within the `.data` section and Windows-specific TLS.

- The version resilience test had 2 major bugs in it
  1. It was not properly specifying references, so references to other dlls were not being handled
  2. It was generating .ni.dll files, which are not actually loaded by the runtime anymore, so even for the code it did generate, the cross module references were not in use.

Version resiliency bugs also fixed
- Fix assertion when handling fields of sequential/explicit types from another module, where we did not generate a correct cross module version resilient fixup. (That's what the fix is in CorInfoImpl.ReadyToRun.cs)
- Disable cross version bubble p/invoke inlining, as we don't currently generate valid cross module tokens for that scenario

Also during this effort a new bug #71507 was discovered. 

* Use llvm-objcopy with StripSymbols=true and clang

* Allow user to override ObjCopyName property

* Quote utilities in Exec calls

* Delete CppCompiler property

* Make dotnet-pgo capable of handling dll conflicts by providing deconfliction options
Co-authored-by: NJakob Botsch Nielsen <Jakob.botsch.nielsen@gmail.com>

* [wasm] Add runArgs.json for console projects

* [wasm] Fix `dotnet.js.symbols` being copied to the bundle

.. and enable it by default for the template projects.

Brings in new cmake 2.23.1 and Android NDK23c which fixes an issue with the binary size and perf of libmonosgen-2.0.so

In NDK23b they decided to no longer pass -O2 compiler optimization flag (for arm64, armv7 used -Oz) as part of the Android toolchain but delegate to upstream CMake behavior: https://github.com/android/ndk/wiki/Changelog-r23 and https://github.com/android/ndk/issues/1536

CMake defaults to -O3 for Release builds but unfortunately this causes quite a noticable binary size increase and perf regression.

The Xamarin Android team measured startup time on an average of 10 runs of `dotnet new maui` on a Pixel 5:
```
-O3: 893.7ms
-O2: 600.2ms
-Oz: 649.1ms
```

We now explicitly pass in -O2 for Android builds.

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

Move Serialization/Cache/Transactions/Syndication issues and PR's into the 'Tellurium' project for attention. (#68193)

* Implement new metadata knobs as internal APIs

* Update src/libraries/System.Text.Json/Common/JsonHelpers.cs

E.g.,

Update LSRA "Allocating Registers" table description.

Dump nodes added during resolution, e.g.:
```
   BB29 bottom (BB08->BB08): move V25 from STK to rdi (Critical)
N001 (  1,  1) [001174] ----------z                 t1174 =    LCL_VAR   int    V25 cse4          rdi REG rdi
```

Dump more data in the LSRA block sequence data:
```
-BB03( 16   )
-BB04(  4   )
+BB03 ( 16   ) critical-in critical-out
+BB04 (  4   ) critical-out
```

When dumping various flow bitvectors, annotate the bitvectors better:
```
-BB25 in gen out
-0000000000000000
-0000000000000003 CSE #01.c
-0000000000000003 CSE #01.c
+BB25
+ in: 0000000000000000
+gen: 0000000000000003 CSE #01.c
+out: 0000000000000003 CSE #01.c
```

Dump hoisting bitvectors using the sorting number:
```
-  USEDEF  (5)={V04 V00 V01 V02 V03}
+  USEDEF  (5)={V00 V01 V02 V03 V04}
```

Also, fix various typos and formatting.

* Implement proposal for `System.Linq`

* Implement proposal for `System.Linq.Queryable`

* Add documentation

* Merge branch 'main' into issue-67194

* Add more test cases

* Apply suggestions
Co-Authored-By: NEirik Tsarpalis <2813363+eiriktsarpalis@users.noreply.github.com>

* Remove unneccesary keyless stuff

* Add more Queryable test cases

* Eliminate `keySelector` null-check in ctor

* Add null checks to `ThenBy`

* Revert "Eliminate `keySelector` null-check in ctor"

This reverts commit 879421b9a5e6d0fba02f0b50cd253eba16f53259.

* Add tests for CreateOrderedEnumerable

* Apply suggestions

* Fix null checks

* Fix null checks

* Update src/libraries/System.Linq/src/System/Linq/OrderBy.cs

* Update src/libraries/System.Linq/src/System/Linq/OrderBy.cs
Co-authored-by: NEirik Tsarpalis <2813363+eiriktsarpalis@users.noreply.github.com>
Co-authored-by: NEirik Tsarpalis <eirik.tsarpalis@gmail.com>

* Exclude root folder .md files as well

* Dummy change in .md file

* fix the wildcard

* Revert "Dummy change in .md file"

This reverts commit ca4decb18221db7d0dff7eee22e33e4ad4784411.

Fixes #70555

[main] Update dependencies from dotnet/xharness dotnet/runtime-assets dotnet/roslyn-analyzers (#71376)

[main] Update dependencies from dotnet/xharness dotnet/runtime-assets dotnet/roslyn-analyzers

*    new ref assembly System.Runtime.InteropServices.JavaScript - empty
*    new src assembly System.Runtime.InteropServices.JavaScript
        moved all implementation from System.Private.Runtime.InteropServices.JavaScript into it
*    added IMPORTS, EXPORTS to js API
*    refactored setup_managed_proxy and teardown_managed_proxy in JS
*    added more range assert for working with wasm memory in JS

This makes the rsp file work regardless of the current directory and makes it much easier for reproducing issues.

So far all of the other paths in the file are generated as absolute paths, except for the rd.xml file path.

* Implement NTLM quirk in NegotiateStreamPal.Encrypt/Decrypt

NegotiateStream on non-encrypted connections with NTLM sends the
messages in a special `<signature token><plain text message>` format.
That's not something that gss_wrap/gss_unwrap would produce. It can be
produced through gss_get_mic/gss_verify_mic calls though so let's do
that.

* Remove MakeSignature/VerifySignature from SspiCli interop

The method names were misleading since they wrapped the EncryptMessage
and DecryptMessage native APIs and not the MakeSignature/VerifySignature
APIs that also exist.

* Remove unused sequenceNumber parameters in NegotiateStreamPal.Encrypt/Decrypt

The SSPI / GSSAPI providers keep track of the sequence numbers
themselves.

* Replace NTAuthentication.MakeSignature/VerifySignature with Wrap/Unwrap

This maps directly to the semantics of gss_wrap/gss_unwrap methods
that are used in many specifications. It replaces the misleading name
which in SSPI API is an equivalent of gss_get_mic/gss_verify_mic.
It also fixes the declaration to actually decode the buffers both
on Windows and Unix. In NTLM the content of the message is sealed
and needs to be decoded.

Note that previously on Unix the VerifySignature API didn't decode the
content. On Windows it did decode the content inside a buffer that was
passed as ReadOnlySpan<byte> but it didn't communicate back the offset
of the decoded data.

The SMTP GSSAPI authentication code was thus reading incorrect data.
In case the underlying authentication was Kerberos the data were
not encrypted and they were located at the beginning of the buffer
so it was not an issue. In case the underlying authentication was
NTLM it was looking at the NTLM signature token which luckily
happens to always start with the bytes 01 00 00 00. That exactly
matched the expected value by accident.

* Fix processing of last SMTP GSSAPI token

The last token in the GSSAPI SASL authentication mechanism is a bit
mask that specifies the supported security protections offered by the
server and the maximum token size. The client is supposed to choose
one of the protections and reply back. Relax the check to actually
support servers that offer anything but "no protection". As long
as the server also offers no protection we can choose it.

* Update unit test to use the new Wrap/Unwrap APIs

* Reset NTLM keys after successful Negotiate authentication

Updated the managed NTLM implementation and the fake servers to
implement the specification quirk:

MS-SPNG section 3.2.5.1 NTLM RC4 Key State for MechListMIC and First
Signed Message specifies that the RC4 sealing keys are reset back to
the initial state for the first message.

Since the managed implementation doesn't expose encryption yet it
didn't affect any observable behavior. Likewise the fake servers
didn't need this code path yet.

* Add GSSAPI authentication test to the loopback SMTP server

* Workaround for https://github.com/gssapi/gss-ntlmssp/issues/77

* Expose the confidentiality flag from the native gss_wrap/unwrap APIs

* Allow default credentials for NTLM server-side on Linux/macOS

* fixing a typo in copying pdb files

* FB

Contributes to #70684

* [wasm][nodejs] Ensure that stdout/stderr have been flushed out before exiting

When the results xml is large, and we are writing the base64
representation in one line, `node` can exit before all the output gets
flushed out. This results in xharness getting an incomplete
`STARTRESULTXML <len> <base64> ... ` with missing `ENDRESULTXML`, thus
no `testResults.xml` is generated.

This can be seen in the case of `Microsoft.Extensions.Primitives.Tests`
which has xml ~140KB, and `System.Memory.Tests` which has a xml ~13MB.

So, wait for the two streams to be flushed out, with a timeout of 3secs.

* [wasm] Wasm.Build.Tests: improve reading output from processes

- Fix to call `WaitForExit()` once `WaitForExit(int)` returns, which
  ensures that all the async handlers have been run.

- Also, for non-browser xharness runs use the emitted `wasm-console.log`
  as the output, so we don't depend on xharness' stdout.

* Wasm.Build.Tests: Run the crypto test only with browser. Other cases are covered in library tests

* Enable WasmTemplateTests.ConsolePublishAndRun

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

* Wasm.Build.Tests: avoid unncessary copy when building locally

Copy sdk for testing workloads only on CI.

* Address feedback from @kg

* Remove timeout on flushing stdout/stderr streams, for console templates, IOW, user apps

Adding GT_NULLCHECK nodes requires knowledge of which basic block the
nullcheck will end up in. We do not have this easily available in all
places this method is called, and regardless using GT_NULLCHECK here has
minimal diffs.

Fix #71193

* #71252 disable AtanPiTest on Android x86

* [wasm] InterpToNativeGenerator: use invariant culture when generating C

.. functions.

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

* Add missing file

Allow specifying the in/ref/out marshaller scenarios for the generator factory and use the element scenarios types for element scenarios.

Also fix a typo in the CollectionsOfCollectionsStress test that implementing this exposed.

* Implement NarrowUtf16ToAscii for AArch64

* Combine x64 and AArch64 implementations of NarrowUtf16ToAscii intrinsic

* Improve comments in VectorContainsNonAsciiChar

* Copy RijndaelManagedTransform from reference source

Copied from https://github.com/microsoft/referencesource/blob/5697c29004a34d80acdaf5742d7e699022c64ecd/mscorlib/system/security/cryptography/rijndaelmanagedtransform.cs

* Format document

* Clean up RijndaelManagedTransform

1. Add copyright
2. Remove unnecessary attributes
3. Mark class as internal
4. Remove FEATURE_CRYPTO define. Only support CipherMode.CBC and PaddingMode.PKCS7.
5. Remove Contracts and replace with Debug.Assert.

* Get RijndaelManagedTransform to compile successfully.

* Make RijndaelManagedTransform implement ILiteSymmetricCipher

And hook it up to AesImplementation for Browser.

* Enable all the Aes tests on Browser.

Mark Aes APIs as supported on Browser.

* Mark all CipherModes and PaddingModes other than CBC and PKCS7 as unsupported on Browser

* Make fields readonly and rename according to code style.

* Replace RijndaelManagedTransformMode with bool encrypting.

* Throw PNSE for unsupported CipherMode and PaddingMode.

Remove unnecessary parameters and fields that aren't supported.

* Fix DecryptorReuse_LeadsToSameResults test so it works on Browser and passes for all CipherModes on other platforms

* Spanify the input buffer in RijndaelManagedTransform Transform and TransformFinal.

* First round of PR feedback

* Make _Nb constant BlockSizeInts

* Get rid of unnecessary allocations

* Remove unsafe pointers from RijndaelManagedTransform.

* PR feedback

Encrypt and Decrypt index arrays are constant values.
Use CopyTo in more places.

* Rename RijndaelManagedTransform => AesManagedTransform

* Change AesManagedTransform to no longer do padding.

Instead, reuse the UniversalCrypto infrastructure to do padding.

* Remove UnsupportedPlatform for PaddingMode

* PR feedback

- clean up unnecessary changes

* PR feedback

Remove UnsupportedOSPlatform("browser") from CipherMode and the SymmetricAlgorithm base class. These create too many false positives and aren't technically accurate since other implementations may support these on browser.

* Use llvm-objcopy for regular and cross builds

This change enables using llvm-objcopy instead of the gnu objcopy for
building runtime. The benefit for cross build is that the host machine
no longer needs to have cross-architecture gnu objcopy installed.

There was an attempt to enable llvm objcopy in the past, but it was
reverted due to a problem with objcopy in llvm 9 that incorrectly
didn't strip debug symbols when `--strip-unneeded` option was specified.
I have fixed that by adding `--strip-debug` in addition to the`--strip-unneeded`.

* Fix OSX build, reflect PR feedback

Currently, EH funclets are placed after the function's main body in memory.
Via the heuristic that EH funclets are infrequently run, this enables a simple splitting implementation:
* If we find a good split point in the function's main body, split there as usual.
* Else if the function has exception handling,
   * Check that all the EH funclets are cold. If any of the funclets are frequently run, don't bother splitting at all.
   * If all of the EH funclets are cold, split at `fgFirstFuncletBB`, so that all EH funclets are placed in the cold section.

Check layout compatibility before morphing `OBJ(ADDR(LCL_VAR))` into a list of promoted fields (#71348)

* Fix non-x86 targets

* Fix x86

* Add tests

* Arm64: local morph

* Arm64: morph

* Fix MultiregStructArgs up

* Spill split args on non-ARM targets

* Add a test

* Work around vectors in varargs being broken