Always use the same TLS context as the runtime for back-deployed concurrency #39556
+20
−8
Conversation
…urrency The exclusivity checking support for concurrency relies on having access to the thread-local set of active memory accesses. Teach the back-deployed concurrency library to use the same TLS context as the runtime, which fortunately hasn't change. This fixes the concurrency exclusivity-checking test in back-deployed configurations that's tracked by rdar://83064974.
|
@swift-ci please test |
|
Verified the change locally on an older system as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
The exclusivity checking support for concurrency relies on having access
to the thread-local set of active memory accesses. Teach the
back-deployed concurrency library to use the same TLS context as the
runtime, which fortunately hasn't change. This fixes the
concurrency exclusivity-checking test in back-deployed configurations
that's tracked by rdar://83064974.
The text was updated successfully, but these errors were encountered: