Skip to content

[Observation] Use independent locking since the runtime functions reference a symbol that is not emitted #81185

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

phausler
Copy link
Contributor

@phausler phausler commented Apr 29, 2025

The runtime functions for locking end up referencing a symbol that is not publicly emitted. This leads to broken linux builds.
Since that interface is not public and does not offer a stable mechanism and Synchronization cannot be used (due to it being a higher deployment target) instead it has to revert to implementing locking from scratch for all platforms.

This is mostly replicated from the swift-async-algorithms package and should be usable enough to accomplish the goals of this module.

Resolves rdar://150060874

@phausler phausler force-pushed the pr/observation_independent_locking branch from 10561de to e5ce709 Compare April 30, 2025 16:09
@phausler
Copy link
Contributor Author

@swift-ci please smoke test

@phausler
Copy link
Contributor Author

phausler commented May 1, 2025

@swift-ci please smoke test linux

@phausler phausler merged commit 3f157ab into swiftlang:main May 2, 2025
3 checks passed
@lhoward
Copy link
Contributor

lhoward commented May 16, 2025

Can we see this back ported to 6.1?

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