Skip to content

Swift-next Cherry-pick: Swift async calling conventions #3060

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

etcwilde
Copy link
Member

This code is necessary for building the next swift compiler on the next llvm.
It was merged into current after things stabilized I guess(?), so it wasn't merged into the next branch.

rdar://79631095

 This change is intended as initial setup. The plan is to add
 more semantic checks later. Most of the code closely mirrors
 that for the Swift calling convention. Three places are
 marked as [FIXME: swiftasynccc]; those will be addressed in
 follow-up commits.

 Differential Revision: https://reviews.llvm.org/D95561

 (cherry-pick to apple/stable/20210107 from not-yet-merged
  revision)
swifttailcc is a new calling convention in LLVM introduced
in https://reviews.llvm.org/D95443. We add a new DWARF tag to capture
this in debuginfo.

Differential Revision: https://reviews.llvm.org/D95704

(cherry-pick to apple/stable/20210107 from not-yet-merged revision)
1. It should be mapped to LLVM's swifttailcc, which is now available.
2. We should make sure we generate a tail call instead of an ordinary call.

Fixes rdar://73762895.

Differential Revision: https://reviews.llvm.org/D95984
@etcwilde etcwilde added the swift-next Requests for fixing swift/next branch label Jun 26, 2021
@etcwilde etcwilde merged commit 0fa8fb6 into swiftlang:swift/next Jun 30, 2021
edymtt pushed a commit to edymtt/llvm-project that referenced this pull request Jul 8, 2021
…ft-async-calling-conventions

Swift-next Cherry-pick: Swift async calling conventions

(cherry picked from commit 0fa8fb6)
@aschwaighofer
Copy link

These patches should have come from llvm.org upstream. @varungandhi-apple it should now be possible to commit those patches because Tim has upstreamed swiftasync support. Can you upstream or commit the patches in review?

@varungandhi-apple
Copy link

Yes, I made some updates, working on landing them.

@etcwilde etcwilde deleted the ewilde/swift-next/swift-async-calling-conventions branch January 26, 2022 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
swift-next Requests for fixing swift/next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants