Skip to content
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

backport 1.10: create phantom task for GC threads (#53815) #54632

Merged
merged 2 commits into from
May 31, 2024

Conversation

KristofferC
Copy link
Sponsor Member

A common idiom used throughout the codebase is to get a pointer to thread-local-state through jl_current_task->ptls.

Create a phantom task for GC threads so that we can make use of this idiom when running in the GC threads as well.

Idea originally suggested by @vchuravy, bugs are mine.

(cherry picked from commit 9636ef7)

A common idiom used throughout the codebase is to get a pointer to
thread-local-state through `jl_current_task->ptls`.

Create a phantom task for GC threads so that we can make use of this
idiom when running in the GC threads as well.

Idea originally suggested by @vchuravy, bugs are mine.

(cherry picked from commit 9636ef7)
@KristofferC KristofferC mentioned this pull request May 30, 2024
23 tasks
Copy link
Contributor

@fingolfin fingolfin left a comment

Choose a reason for hiding this comment

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

Thank you!

@fingolfin
Copy link
Contributor

(I would have happily provided such a PR, too, just to save you work. Apologies if I should just have done that, I am not sure what the right "protocol" is -- you are already doing a ton of work and I don't mean to be a burden)

@KristofferC KristofferC merged commit 61f9847 into release-1.10 May 31, 2024
5 of 6 checks passed
@KristofferC KristofferC deleted the backports-release-1.10 branch May 31, 2024 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants