-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[IRGen][wasm] Disable manual indirection for coroutine yielding results #85358
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
base: main
Are you sure you want to change the base?
Conversation
|
swiftlang/llvm-project#11765 |
aa3ca98 to
f6b81f8
Compare
|
swiftlang/llvm-project#11765 |
f6b81f8 to
04cebc5
Compare
|
swiftlang/llvm-project#11765 |
04cebc5 to
e16f4df
Compare
|
swiftlang/llvm-project#11765 |
1 similar comment
|
swiftlang/llvm-project#11765 |
e16f4df to
3c16fba
Compare
|
swiftlang/llvm-project#11765 |
`clang::CodeGen::swiftcall::shouldPassIndirectly` now returns true for multiple scalar values on wasm targets because the Wasm MVP does not support multiple return values. For such targets where we can't directly return two pointers, we should not attempt to indirect at this stage because the later MC lowering will also indirect the return.
3c16fba to
f53fad9
Compare
|
swiftlang/llvm-project#11765 |
clang::CodeGen::swiftcall::shouldPassIndirectlynow returns true for multiple scalar values on wasm targets because the Wasm MVP does not support multiple return values. For such targets where we can't directly return two pointers, we should not attempt to indirect at this stage because the later MC lowering will also indirect the return.