-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[TBDGen] Use effective linkage for class member async function pointers. #35437
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
Conversation
@swift-ci please test |
0365a46
to
9ec9fca
Compare
@swift-ci please test |
Build failed |
9ec9fca
to
bbf127f
Compare
@swift-ci please test |
Build failed |
bbf127f
to
55870ad
Compare
@swift-ci please test |
Build failed |
55870ad
to
9084607
Compare
@swift-ci please test |
Build failed |
@swift-ci please test linux platform |
Previously, the "bare" linkage of a link entity was used to determine whether to put an async function pointer into the tbd. That did not match the mechanism by which the linkage was determined in IRGen. There, the linkage is the "_effective_" linkage (i.e. the value returned from SILFunction::getEffectiveSymbolLinkage). Here, whether to put the async function pointer corresponding to a class method is determined on the basis of that effective linkage. rdar://problem/73203508
9084607
to
2e880af
Compare
@swift-ci please test |
Build failed |
@swift-ci please test macos platform |
Build failed |
@swift-ci please test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
Build failed |
@swift-ci please clean test linux platform |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please test macos platform |
Build failed |
@swift-ci please clean test macos platform |
Build failed |
@swift-ci please smoke test macos platform |
@swift-ci please test macos platform |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 Seems this will fix a crasher I'm encountering, looks good though have not verified yet (would need to build a toolchain meh)
Previously, the "bare" linkage of a link entity was used to determine whether to put an async function pointer into the tbd. That did not match the mechanism by which the linkage was determined in IRGen. There, the linkage is the "effective" linkage (i.e. the value returned from SILFunction::getEffectiveSymbolLinkage).
Here, whether to put the async function pointer corresponding to a class method is determined on the basis of that effective linkage.
rdar://problem/73203508