[IRGen][wasm] Support ABIs with differing indirect rules for results and arguments #85358
Conversation
|
swiftlang/llvm-project#11765 |
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
aa3ca98 to
f6b81f8
Compare
|
swiftlang/llvm-project#11765 |
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
f6b81f8 to
04cebc5
Compare
|
swiftlang/llvm-project#11765 |
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
04cebc5 to
e16f4df
Compare
|
swiftlang/llvm-project#11765 |
1 similar comment
|
swiftlang/llvm-project#11765 |
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
e16f4df to
3c16fba
Compare
|
swiftlang/llvm-project#11765 |
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
3c16fba to
f53fad9
Compare
|
swiftlang/llvm-project#11765 |
1 similar comment
|
swiftlang/llvm-project#11765 |
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
f53fad9 to
2ffa49c
Compare
kateinoigakukun
changed the title
|
swiftlang/llvm-project#11765 |
|
@swift-ci please test source compatibility |
`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.
SIMD2<Float> is not a legal vector type for wasm and thus cannot be returned directly as a vector value. See SwiftABIInfo::isLegalVectorType
kateinoigakukun
force-pushed
the
yt/wasm-sret
branch
from
2ffa49c to
0d0595d
Compare
|
swiftlang/llvm-project#11765 |
|
@swift-ci please test source compatibility |
|
@swift-ci build toolchain Windows platform |
|
@swift-ci smoke test |
|
@swift-ci smoke test Windows platform |
|
swiftlang/llvm-project#11765 |
|
swiftlang/llvm-project#11765 |
|
swiftlang/llvm-project#11765 |
1 participant
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.