* add correct value when cloning http headers

* Address PR feedback
Co-authored-by: NTomas Weinfurt <furt@Shining.local>
Co-authored-by: NStephen Toub <stoub@microsoft.com>
Co-authored-by: NTomas Weinfurt <tweinfurt@yahoo.com>
Co-authored-by: NTomas Weinfurt <furt@Shining.local>

* Add new IntPtr/UIntPtr API surface (#307)

* Add new IntPtr surface

* Add new UIntPtr API surface

* Add sequential layout to match [U]Int32

* Add interfaces and sequential layout

* Add interfaces

* Add namespaces

* Add namespaces

* Update UIntPtr.cs

* Update IntPtr.cs

* Change style

* make non versionable, elide copy

* fix style, elide copy, make non versionable

* Fix syntax error

* Fix style issues

* Fix style issues

* Update IntPtr.cs

* Update UIntPtr.cs

* Update ref assembly

* Allow comparison of intptr/uintptr in Array

* Fixed ELEMENT_TYPE cases, added tests based on Int32/UInt32 tests

* Fixes

* Update Array.cs

* Update Array.cs

* Update Array.cs

* Update ArrayTests.cs

* Update ArrayTests.cs

* Update UIntPtrTests.cs

* Update ArrayTests.cs

* fix instance methods??

* fixes

* Fixwa

* fix tests

* Add non versionables

* fix compare methods

* Fix comparison error

* fix boundary

* fix compares

* fix maxvals

* remove xunit buggy data

* silly var name error

* Update src/libraries/System.Private.CoreLib/src/Resources/Strings.resx
Co-Authored-By: NTanner Gooding <tagoo@outlook.com>

* Fix ToString
Co-authored-by: NTanner Gooding <tagoo@outlook.com>

* Remove the explicit IEquatable implementation from the IntPtr/UIntPtr reference API
Co-authored-by: NJohn <johnkellyoxford@gmail.com>

* System.Diagnostics Tracing APIs

* address the feedback

Manually add publishing for p4 and p5 channels while arcade is not flowing

See https://github.com/mono/mono/issues/19603Co-authored-by: Nakoeplinger <akoeplinger@users.noreply.github.com>

* Override IsByRefLike on S.R.E.*Builder classes

Fixes #8828

* Adds tests

* Update System.Reflection.Emit.Tests.csproj

* Bumping CI

* Update mono as well

- This was prompted by vscode/vs requiring this for array expansion.
- It runs a given js function string, on a given object id.
- We handle the case for dotnet object ids.

Implementation:

- We build a proxy object that reflects the details of the real dotnet object/array
- And run the js function on that proxy object

- Then if `returnByValue` was requested, the result is returned as-is
- Else we cache that object, with a new special object id (`dotnet:cfo_res:..`),
  and return that id in the response.

- Subsequently, we would get `Runtime.getProperties` request on this new object id
- And a `Runtime.releaseObject` request, to free that function result.

- All this is handled currently

Tests:

- A few tests were added which invoke `callFunctionOn`, on JS objects, and checks the result
  - And the same checks are performed on equivalent dotnet objects, with the same js function
  - This should help stay in sync with what we think `callFunctionOn` should work as

  - These tests have an additional parameter - `roundtrip`, which calls a simple function
	`function () { return this; }`
    .. on a dotnet object, and gets the result object id. If `roundtrip == true`, then it
    runs that same function on the result object, and gets a new result object id. And the
    tests run their checks on that.

    - this helps to check that outside of the proxy, the result object behaves same as any
      other dotnet object.

- Also, most of the tests were modified to support an additional mode (`use_cfo`).
  - With this, whenever a test wants to run `Runtime.getProperties on an object, we pass that
    object through the earlier "identity" function, and then run `getProperties` on that
    resultant object.

  - This helps to take advantage most of the existing tests, and use them for `callFunctionOn`
    testing too, by ensuring that the results of CFO returns results same as any other object.

Fixes mono/mono#19229, mono/mono#19531
Co-authored-by: Nradical <radical@users.noreply.github.com>

* Add Advertise IPC Command
* Update diagnostics server to use both reverse and traditional modes
* Change DOTNET_DiagnosticsServerAddress to DOTNET_DiagnosticsMonitorAddress and only use for reverse connection
* Add IpcStreamFactory abstraction
* IpcStreamFactory::Poll is now more similar to the poll API from Linux
* IpcPollHandle struct is used to abstract listening for client and server connections
* use overlapped io for all io on windows
* Add ConnectionState abstraction
* Implement timeout read/write

Add a bundler consistency tests that verifies that the size of each embedded file
(recorded in the bundle manifest) matches its original size of the file on disk.

Helps fix issue: https://issuetracker.unity3d.com/issues/unity-crashes-when-opening-the-project

We were hitting a crash were a corrupted dll would get loaded and then hit an assert later on when something tried to use it. The verifier suite would correctly identify the dll as corrupt but it was impossible to turn on just the PE verification. I've added a new PE only mode above "off" to allow for just the PE verifier to be used instead of the larger verification suite.
Co-authored-by: NUnityAlex <UnityAlex@users.noreply.github.com>

PR adds an optional stream termination handling to `Http2LoopbackConnection.ReadBodyAsync` and fixes `HttpClient` construction missing the `SocketHttpHandler` created in the test.

Fixes #31220

Unlike the other resolvers, this one *can* exist on the default ALC, so we have to add the null check like in GetAssemblyLoadContext.

Move the now-unused ResolveUsingResolvingEvent method back to the CoreCLR-specific file.

* No null check in Get.

* bypass AuxData

[mono] Fix multidimensional array construction when using programmer-specified lower bounds. (#35091)

* [mono] Fix multidimensional array construction when using programmer-specified lower bounds.

mono_array_full_new_checked and mono_array_full_new (which is marked as
a MONO_API function) both take two pointers to buffers containing
lengths and lower bounds. mono_array_new_n_icall can split the incoming
parameter list in two before forwarding the results to
mono_array_full_new_checked, so mono_array_full_new_checked was
receiving two buffers containing interleaved lower bounds and lengths.

ECMA-335 states that array constructors that specify both lower bounds
and lengths interleave these values. Deinterleave these
in method_to_ir.

Add some tests to iltests.il that verify that multidimensional arrays
with custom lower bounds work.

Fixes https://github.com/dotnet/runtime/issues/34377.
Fixes https://github.com/dotnet/runtime/issues/34378.
Fixes https://github.com/dotnet/runtime/issues/34381.

* Deinterleave lower bounds and array lengths in the interpreter.

Also make the condition in which the deinterleaving code path is taken
more precise. Perhaps this branch should be marked as unlikely.

* Fix a typo.
Co-authored-by: Nimhameed <imhameed@users.noreply.github.com>

To avoid confusion with `Func<>` delegate and object. At least to me it create a bit of unnecessary confusion. Whether this should be `Method` or just `F` can be discussed. However, `Method` makes it clear the discussion is about a generic **method** instantiation.

* [meta] Expose managed ALC fields to the runtime

* [meta] Add mono_assembly_load_full_alc to unstable

* [loader] Add preload hook V3 for netcore embedding API

* [loader] Add append parameter to preload hook V3 installation

* [meta] Fix ALC usage to be netcore-only

* Move Sequential attribute to Mono ALC declaration

* Feedback

* fix ping on OSX when running as root

* feedback from review

* limit disabling DualMode to OSX

* fix osx
Co-authored-by: NTomas Weinfurt <furt@Shining.local>

* try to add FreeBSD to the build

* s/FreeBSD/FReeBSD_x64

* more fixes to pass -os FreeBSD

* add missing :

* more fixes and feedback from review

* pull in new container

* fix corelib-nativecorelib-tools-packages as well

* add crossrootfsDir

* pass crossrootfsDir

* fix installr

* fix compilation on freebsd

* fix test build on freebsd

* update to match new layout

* fix native tests

* CrossBuild?

* rootfsDir debug

* merge with linux to get container support

* fix proc_maps

* fix up buildCommandSourcesDirectory

* remove debug

* more fixup for buildCommandSourcesDirectory

* use TargetOS instead of os

* remove old section

* rever changes to get_loaded_library_from_proc_maps

* fix compilation with missing getline

* add official build

* use arch

* remove special pool for freebsd

* roll-back runtime-official.yml
Co-authored-by: NTomas Weinfurt <furt@Shining.local>
Co-authored-by: NTomas Weinfurt <furt@tocherni-t490s.middleeast.corp.microsoft.com>

- Microsoft.NET.Test.Sdk: 16.7.0-preview-20200408-06 -> 16.7.0-preview-20200416-02
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

* Enclose paths with quotes in testPackages.proj

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

As we ContinueOnError and error by reading from the ExitCode property we can set IgnoreExitCode in the msbuild Exec invocation to avoid the following verbose output: `error MSB4132: The "Exec" task returned false but did not log an error.`

Co-authored-by: NSteve Pfister <steve.pfister@microsoft.com>

* Adding a regression test to validate the Sse.CompareGreaterThan and related behaviors

* Fixing several of the Sse/Sse2.Compare* intrinsics to account for NaN inputs

* Applying format patch

* Switch to using compOpportunisticallyDependsOn

* Use the named intrinsic comparison macros rather than magic numbers

* Applying formatting patch

* Define the _CMP hwintrinsic macros since they aren't available by default on Unix

* Simplifying the special importation logic for Sse/Sse2 compare GreaterThan functions

* Applying formatting patch

* Add a comment explaining the naming of the _CMP_* macros used by the x86 HWIntrinsics

* Switch to mirroring the FloatComparisonMode enum rather than using the _CMP_* macros

* Apply formatting patch

* Don't use XML style doc comments for the FloatComparisonMode mirror on the C++ side

* Ensure the base type is set before it is checked

* Applying formatting patch

* Added test for Issue 30218, use of resource Sch_MinLengthGtBaseMinLength

* Reworded error message to remove the invalid formatters.

Issue #30218

* Updated check of message from the exception to be more amenable to potential internationalization.

* Reworded resource Sch_MaxLengthGtBaseMaxLength and added unit test for same.

* Simplified test code per feedback from Dan Moseley, PR#33890.

* Tests to increase code coverage.   The ones that are failing trigger resource string Sch_MaxMinLengthBaseLength to be used as the Exception message.

* Removed invalid formatters from the resource string Sch_MaxMinLengthBaseLength.  Failing tests from the previous commit now pass.

* Added test for the Exception using string resource Sch_LengthGtBaseLength as its message.  This covers a source line and branch not previously covered.  This test fails due to the invalid formatters.

* Reworded string resource Sch_LengthGtBaseLength to remove the invalid formatters.

* Added unit tests for uses of string resource Sch_FacetBaseFixed.

* Made test for the message containing "fixed" more specific.

* Reworded string resource Sch_FacetBaseFixed to remove the invalid formatter.

* Added unit test to cover usage of string resource Sch_InvalidAllMax.  A second usage of this string resource is not covered as it is in a class marked Obsolete.

* Reworded string resource Sch_InvalidAllMax to remove the invalid formatter.

* Added unit test for String Resource Sch_InvalidAllElementMax - invalid formatter.

* Reworded string resource Sch_InvalidAllElementMax to remove the invalid formatter.

* Added unit test which causes an XmlSchemaException using string resource Sch_InvalidExemplar as its message.

* Reworded Sch_InvalidExemplar to remove the invalid formatter.  Also, added the name of the element which cannot be used as the substitution group affiliation.

* Added unit test that causes an XmlSchemaException to be thrown using string resource Sch_GroupBaseRestNotEmptiable as its message.

* Removed the curly braces so there are no longer any invalid formatters.

* Added unit tests that cause an XmlSchemaException to be thrown using string resource Sch_AllRefMinMax as its message.

* Changed string resource Sch_AllRefMinMax to remove the invalid formatters.

* reworded Sch_MinLengthGtBaseMinLength and Sch_MaxLengthGtBaseMaxLength similarly to Sch_LengthGtBaseLength

* Corrected error "greater than" to "less than".

* Changed name of test to more accurately  reflect its purpose.

* Changed casing of MinLength and MaxLength to match their XML facets.  Removed redundant ToLower call and comment.

* Removed all Regex used to find invalid formatters.

* renamed MaxMinLengthBaseLength_TestData to indicate that this is testing the successful case.

* Removed suppression of exception so that we will see the exception if one is thrown.

* Removed comments as there are issues tracking these.

* Fixed comment larger -> lower.

* Removed XML comments on test methods.

* Removal of XML comment that was missed.

* Native COM clients have not been running since we switched over to SDK projects.

* Stop IL generators from passing GC types to unmanaged function calls.
Update crossgen2 IL stub generators.
Update Dynamic runtime stub generator.
Add assert for GC types in unmanaged function calls.

* Rename ReadyToRun.SuperIlc to just R2RTest to save typing

* Apply the SuperIlc -> R2RTest rename to crossgen determinism test

When the last reference to a collectible AssemblyLoadContext goes away,
its finalizer is called on the finalizer thread. It ends up calling the
native CLRPrivBinderAssemblyLoadContext::PrepareForLoadContextRelease
method which replaces a long weak GC handle to the managed
AssemblyLoadContext stored in the CLRPrivBinderAssemblyLoadContext by a
strong GC handle to the same AssemblyLoadContext and closes the original
weak handle.
The problem is that another thread may have read the weak handle pointer
and then try to use it to call into the resolving methods on the managed
AssemblyLoadContext. If that thread tries to resolve the related handle
after the finalizer thread has closed it, it fails as the handle doesn't
exist anymore. It could even get a completely different object if the
handle got reused in between. Or even worse, if the handle got reused by
another AssemblyLoadContext, the handle would resolve, but to the
different AssemblyLoadContext.

This change fixes the problem by keeping the weak handle open and
closing it after the AssemblyLoadContext shutdown completes (there are
no more assemblies that were loaded into that context and no instances
of types from those assemblies). The strong handle now serves only to
keep the managed AssemblyLoadContext alive.

Faster and safer

Co-authored-by: Nradical <radical@users.noreply.github.com>

* profiler tests depend on jit events so disable R2R images via profiler eventmask

* fix RequestReJITWithInliners for R2R modules

* Update tests to work correctly when crossgenned

* fix issue where test was treating an HRESULT as a FunctionID

* fix alpine failures. you can dlopen a relative path in glib, but apparently with musl you have to have the full path. So look at /proc/self/maps to find the full path to the loaded coreclr

* re-enable profiler tests now that they are passing

* Code review feedback

* Update rejit.cpp

* Enable cross OS DBI build

* Fix .gitignore

* Fix Cross OS DBI compilation issues

* Review feedback

* Cleanup dummy/twowaypipe.cpp

Fixes #35111

With the net5.0 TFM change and the nuget static graph restore, we require VS >= 16.6 Preview2.