Skip to content

C ABI Changes for wasm32-unknown-unknown #1531

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

Merged
merged 11 commits into from
Apr 4, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update wording
  • Loading branch information
alexcrichton committed Apr 3, 2025
commit 12c30430d58212c07778266bef9ec2cd53bd97ba
4 changes: 2 additions & 2 deletions content/c-abi-changes-for-wasm32-unknown-unknown.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,8 +194,8 @@ To determine the impact to your project there are a few tools at your disposal:
Code can use `-Zwasm-c-abi=spec` to use the standard definition of the C ABI
for a crate to test out if changes work.

The best way to test your crate is to compile with a `nightly-2025-03-27`
compiler, ensure there are no warnings, and then test your project still works
The best way to test your crate is to compile with `nightly-2025-03-27`
or later, ensure there are no warnings, and then test your project still works
with `-Zwasm-c-abi=spec`. If all that passes then you're good to go and the
upcoming change to the C ABI will not affect your project.

Expand Down