* add DefaultPropertyAttribute and DefaultEventAttribute to PrintDocument class and add references to System.ComponentModel.TypeConverter
* add the DefaultPropertyAttribute and DefaultEventAttribute to PrintDocument in the ref
Add DefaultEventAttribute and DefaultPropertyAttribute to PrintDocument in PrintDoument.Unix.cs
This is a fllow-up to #37335 and #37840.
When an inline fails we replace `GT_RET_EXPR`with the
original `GT_CALL` node. `GT_RET_EXPR`may end up in
a basic block other than the original `GT_CALL` so we need
to propagate basic block flags.
Fixes#36588.
If we have a very small root method that calls a large method that is marked with
AggressiveInlining, we may fail to inline because of a budget check.
Allow such inlines to bypass the check.
Closes#38106.
When the `configure` file is touched the autotools build will rerun it without the `emconfigure` wrapper like we do in mono.proj.
This means instead of emscripten's `ar` or `ranlib` we're getting the system tools instead, causing compilation errors like:
```
libmono-icall-table.a: archive is missing an index; Use emar when creating libraries to ensure an index is created
```
Fix this by adding a dependency on configure as well so we rerun the whole autogen.sh process.
* Re-enable Apphost.Bundle.Tests.BundleRename test
* Remove StaticHostApp
StaticHostTest used the StaticHostApp (which is effectively a copy of StandaloneApp) as a work-around for synchronization problems.
Remove this work-around.
* Synchronize GetNewTestArtifactPath()
Add locking around GetNewTestArtifactPath() so that multiple threads attempting to create new copies of a TextFixture don't collide and work on the same path.
Disable more tests failing on Windows ARM64 with the bug
https://github.com/dotnet/runtime/issues/37883
(compDoOldStructRetyping assertion failure in JIT). I think
this is currently the biggest known error bucket in CG2 composite
testing.
Thanks
Tomas
(1) Switch most legs to use composite mode;
(2) Add ARM64 legs;
(3) Add a single non-composite leg;
(4) Reduce the frequency to 3 times a week in view of the increased
level of testing.
Thanks
Tomas
* Update perf proj from arcade
* Add timeout for pr and internal jobs
* Change to a variable that is set
* Escape variable with single quotes
* Change timeout from days to minutes
* Fix typo
* Change to default
In runtime/src/coreclr/src/jit/unwindamd64.cpp line 516
frame register is printed as none if it is RAX,
made the change in extensions.cs to reflect this.:
In the post-call part of a pinvoke inline call frame, it's not safe
to start a stress mode GC in the window between checking
`g_TrapReturningThreads` and the call to `CORINFO_HELP_STOP_FOR_GC`.
The call instruction is already getting special treatement, but there may
be other instructions between the check and call. Instead of trying
to pattern match them all, suppress GC stress if `g_TrapReturningThreads`
is true, the thread is in cooperative mode, and there's an active inline
call frame.
Closes#37236.
Port the managed type system unit tests and wire them up to build.cmd -test so they run if the clr.tools subset is included in compilation.
Port enough USG layout and `Array<T>` support so we can keep their respective tests running in this repo.
* Fix Assertion failed 'rhs != UninitVal()' #35413
Issue was a preHeader blocks was inserted and the compacted with the previous block
and we had a null value for bbReach during compaction.
* Re-enable test b539509
* Update UnmanagedCallersOnlyAttribute API surface
* Update comments and block unknown calling convention types for
UnmanagedCallersOnlyAttribute.
* UnmanagedCallersOnlyAttribute should not be inheritable.
* Bring back System.IO.Pipes.AccessControl package and make it available in .NET 5.0.
* address suggestions
* fix test error
* Microsoft.Windows.Compatibility.pkgproj
These nine tests fail with the JIT assertion failure
'!comp->compDoOldStructRetyping()'. I'm not 100% sure whether this
makes the job green again as I see a somewhat different error in
the AdvSimd_Part3_r test so I'm reluctant to disable it with the
same bug before more investigation.
Thanks
Tomas
* Fix PEFile::GetAssemblyLoadContext during early runtime stages
The PEFile::GetAssemblyLoadContext was asserting if it was called before
the m_pTPABinderContext was created in AppDomain::CreateBinderContext.
That turned out to be a problem for a check performed in
ReadyToRunInfo::Initialize.
This change calls AppDomain::CreateBinderContext from the
PEFile::SetupAssemblyLoadContext instead of calling
AppDomain::GetTPABinderContext. That ensures that the
PEFile::GetAssemblyLoadContext can always return valid
AssemblyLoadContext.
* fix helper multithreading issue -- don't re-read flags that can change
* fix helper logging and abort on error
* change strategy for protecting original method entry block
when doing an OSR compile. Instead of marking it don't remove, use
artificial ref count boost.
I've also annotated CoreCLR's `Type.GetType` in the same spot as Mono. Mono's implementation was triggering warnings, which is what promted me to add it there, but we should annotate this nonetheless because absent intrinsic treatment in Linker, this would be unsafe.
This PR has 2 objectives. First it makes the interp stack allocated in a single contiguous area of memory. This will enable us to do fast pointer bumping when switching between frames and not have to worry about scattered memory fragments. Second, it makes the stack space used by a frame (locals + execution stack) a compile time constant. This could prove useful for future optimizations, because we can tell at compile time at which stack offset every instruction outputs its result. In order to achieve this, localloc memory has been kicked out of the normal stack space into its own allocator, which is almost identical to the old stack fragment allocator.
Co-authored-by: BrzVlad <BrzVlad@users.noreply.github.com>