diff options
| author | Nikita Popov <npopov@redhat.com> | 2024-07-10 17:20:21 +0200 |
|---|---|---|
| committer | Nikita Popov <npopov@redhat.com> | 2024-07-11 12:20:26 +0200 |
| commit | 8a50bcbdceacca60126c085c7cad46aced589c87 (patch) | |
| tree | ad54c95ac9ab358576c4076337b9594fb8600649 /compiler/rustc_codegen_gcc/src/errors.rs | |
| parent | 0fdfb61795b40037955154638fe35f20b16c8e55 (diff) | |
| download | rust-8a50bcbdceacca60126c085c7cad46aced589c87.tar.gz rust-8a50bcbdceacca60126c085c7cad46aced589c87.zip | |
Remove extern "wasm" ABI
Remove the unstable `extern "wasm"` ABI (`wasm_abi` feature tracked in #83788). As discussed in https://github.com/rust-lang/rust/pull/127513#issuecomment-2220410679 and following, this ABI is a failed experiment that did not end up being used for anything. Keeping support for this ABI in LLVM 19 would require us to switch wasm targets to the `experimental-mv` ABI, which we do not want to do. It should be noted that `Abi::Wasm` was internally used for two things: The `-Z wasm-c-abi=legacy` ABI that is still used by default on some wasm targets, and the `extern "wasm"` ABI. Despite both being `Abi::Wasm` internally, they were not the same. An explicit `extern "wasm"` additionally enabled the `+multivalue` feature. I've opted to remove `Abi::Wasm` in this patch entirely, instead of keeping it as an ABI with only internal usage. Both `-Z wasm-c-abi` variants are now treated as part of the normal C ABI, just with different different treatment in adjust_for_foreign_abi.
Diffstat (limited to 'compiler/rustc_codegen_gcc/src/errors.rs')
0 files changed, 0 insertions, 0 deletions