Skip to content

Call the jit shutdown logic on crossgen2 shutdown #56187

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

Merged

Conversation

davidwrighton
Copy link
Member

  • Allows the jit shutdown logic to execute reliably on both Windows and Unix

Fixes #49525

- Allows the jit shutdown logic to execute reliably on both Windows and Unix
@davidwrighton
Copy link
Member Author

@dotnet/crossgen-contrib

Copy link
Contributor

@BruceForstall BruceForstall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thank you!

@davidwrighton davidwrighton merged commit d20fdf1 into dotnet:main Jul 23, 2021
Comment on lines +84 to +93
if (s_jit != IntPtr.Zero)
{
return s_jit;
}

lock(typeof(JitPointerAccessor))
{
s_jit = getJit();
return s_jit;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What thread safety guarantees is the lock giving us here? I would expect a double-checked locking pattern at least.

@ghost ghost locked as resolved and limited conversation to collaborators Aug 22, 2021
@davidwrighton davidwrighton deleted the callProcessShowdownWorkFromCrossgen2 branch April 13, 2023 18:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

crossgen2 doesn't call DllMain on the JIT
4 participants