diff options
| author | bors <bors@rust-lang.org> | 2024-04-19 03:35:10 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-19 03:35:10 +0000 |
| commit | 0f17e5ae235460397a76e848639b7e59ad6c3535 (patch) | |
| tree | 5cb80e79b763bd6ced6a62688fa559d2248dd75c /tests/codegen/patchable-function-entry/patchable-function-entry-no-flag.rs | |
| parent | cccf379a5bd7096b970277db70f72055ff01a5e8 (diff) | |
| parent | d0dc94334bfaf38bbc7c8fb5f7a496093345c344 (diff) | |
| download | rust-0f17e5ae235460397a76e848639b7e59ad6c3535.tar.gz rust-0f17e5ae235460397a76e848639b7e59ad6c3535.zip | |
Auto merge of #117919 - daxpedda:wasm-c-abi, r=wesleywiser
Introduce perma-unstable `wasm-c-abi` flag Now that `wasm-bindgen` v0.2.88 supports the spec-compliant C ABI, the idea is to switch to that in a future version of Rust. In the meantime it would be good to let people test and play around with it. This PR introduces a new perma-unstable `-Zwasm-c-abi` compiler flag, which switches to the new spec-compliant C ABI when targeting `wasm32-unknown-unknown`. Alternatively, we could also stabilize this and then deprecate it when we switch. I will leave this to the Rust maintainers to decide. This is a companion PR to #117918, but they could be merged independently. MCP: https://github.com/rust-lang/compiler-team/issues/703 Tracking issue: https://github.com/rust-lang/rust/issues/122532
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-no-flag.rs')
0 files changed, 0 insertions, 0 deletions