Skip to content

Move CoreCLR over to the managed wait subsystem #117788

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 42 commits into
base: main
Choose a base branch
from

Conversation

jkoritzinsky
Copy link
Member

@jkoritzinsky jkoritzinsky commented Jul 17, 2025

Use the shared managed wait subsystem for CoreCLR's managed code instead of the Win32 PAL

Also, remove the named mutex support from the CoreCLR PAL as nothing uses it now.

TODO: Once #117688 is in, we can remove Mutex support from the Win32 PAL entirely

Unblocks #115685

Depends on #117635

Copy link
Contributor

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

jkoritzinsky and others added 27 commits July 29, 2025 20:32
…ean up a thread's managed logic from the finalizer thread.
…on. Its the only primitive that supports abandoment correctly.
@jkoritzinsky jkoritzinsky force-pushed the coreclr-managed-wait branch from bf32f50 to 934179a Compare July 29, 2025 21:34
@jkoritzinsky jkoritzinsky force-pushed the coreclr-managed-wait branch from 1e7ebc1 to 06de3b2 Compare July 29, 2025 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Threading blocked Issue/PR is blocked on something - see comments runtime-coreclr specific to the CoreCLR runtime
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant