Skip to content

SILGen: Have emitSemanticStore cast off concurrency annotations. #83107

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
merged 1 commit into from
Jul 18, 2025

Conversation

jckarter
Copy link
Contributor

If a function is being semantically treated as having different concurrency annotations because of a @preconcurrency import or language mode setting, then SILGen may try to store an argument or result for a call using a value that differs only in concurrency annotations, which can be safely bitcast away.

Fixes rdar://154520999

@jckarter
Copy link
Contributor Author

@swift-ci Please test

If a function is being semantically treated as having different concurrency
annotations because of a `@preconcurrency` import or language mode setting,
then SILGen may try to store an argument or result for a call using a value
that differs only in concurrency annotations, which can be safely bitcast
away.

Fixes rdar://154520999
@jckarter jckarter force-pushed the semantic-store-preconcurrency branch from 75c639a to 0e94c63 Compare July 16, 2025 19:41
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter
Copy link
Contributor Author

@swift-ci Please test macOS

1 similar comment
@jckarter
Copy link
Contributor Author

@swift-ci Please test macOS

@jckarter jckarter merged commit 2f62342 into swiftlang:main Jul 18, 2025
5 checks passed
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.

2 participants