Skip to content

[lldb] Cherry-pick lost commits during the 6.1 branch #9654

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

felipepiovezan
Copy link

No description provided.

@felipepiovezan
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link

@swift-ci test

@shahmishal shahmishal requested a review from a team November 21, 2024 19:29
This will enable us to share code and handle more functions similar to
swift_task_switch in a subsequent commit.

(cherry picked from commit 92b6c3c)
The use of `async let` in swift introduces two new trampolines that may
trigger a task switch:
1. `swift_asyncLet_get`, which gets called upon `await`ing an `async
   let` variable.
2. `swift_asyncLet_finish`, which gets called when the `async let`
   variable goes out of scope.

We need step through plans for both of those.

(cherry picked from commit 405a791)
@felipepiovezan felipepiovezan force-pushed the felipe/cherry-pick-missing-commits-release branch from 2a83a46 to a81d2d3 Compare December 4, 2024 17:42
@felipepiovezan
Copy link
Author

@swift-ci test

@felipepiovezan
Copy link
Author

Closing in favor of #9691

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