Use function pointers instead of marshalled delegates in EventSource#79970
Use function pointers instead of marshalled delegates in EventSource#79970jkotas merged 5 commits intodotnet:mainfrom
Conversation
src/libraries/System.Private.CoreLib/src/System/Diagnostics/Tracing/EventPipeEventProvider.cs
Show resolved
Hide resolved
src/libraries/System.Private.CoreLib/src/System/Diagnostics/Tracing/EventPipeEventProvider.cs
Show resolved
Hide resolved
…acing/EventPipeEventProvider.cs
src/libraries/System.Private.CoreLib/src/System/Diagnostics/Tracing/EventProvider.cs
Show resolved
Hide resolved
…acing/EventProvider.cs
|
@jkotas this PR has broken unloadability for a couple of coreclr tests on both Windows and Unix. The unloading is blocked due to root like this (the root path differs a bit test by test): The failing tests are: |
|
To repro this, just run the coreclr tests with "runincontext" argument added. Btw, there are few additional failed test that fail due to incompatibilities with unloading that I am working on disabling. |
|
@jkotas can you please take a look when you have a chance? |
|
I have opened #80450 on this. |
Function pointers are more efficient and avoid JITing. This is one of the last remaining uses of marshalled delegates in core framework. It allows the infrastructure for marshalled delegates to be trimmed.