Skip to content

Add cfgs to distinguish WASIp3 and WASIp2 targets - #142

Merged
pchickey merged 13 commits into
bytecodealliance:mainfrom
adamrk:abk/p3-feature-base
Sep 10, 2026
Merged

Add cfgs to distinguish WASIp3 and WASIp2 targets#142
pchickey merged 13 commits into
bytecodealliance:mainfrom
adamrk:abk/p3-feature-base

Conversation

@adamrk

@adamrk adamrk commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Gate WASIp2 specific features behind cfg(all(target_os = "was", target_env = "p2")) to set up WASIp3 implementation.

Addresses #144

@adamrk

adamrk commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

Still investigating the test failure, but I was able to reproduce it on main so it's likely some existing flakiness.

@adamrk

adamrk commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

Fix for the test here: #143

@pchickey pchickey mentioned this pull request Sep 2, 2026
13 tasks
@adamrk
adamrk force-pushed the abk/p3-feature-base branch from 170b21b to ea32edf Compare September 3, 2026 14:24
Comment thread build.rs Outdated
@adamrk
adamrk requested a review from pchickey September 3, 2026 14:26
Comment on lines -32 to +34
rustup default "${{ steps.select.outputs.version }}"
# `rustup default` gets overwritten by rust-toolchain.toml, `rustup
# override` has higher precedence though.
rustup override set "${{ steps.select.outputs.version }}"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: it looks like our previous setup was actually running the stable toolchain for the msrv and nightly jobs because the included rust-toolchain.toml file was overriding the default set here.

Comment thread Cargo.toml
Comment on lines -62 to +67
rust-version = "1.91.1"
rust-version = "1.92.0"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had to bump the msrv because 1.91.1 doesn't have the p3 target_env and using it will throw a warning.

@adamrk adamrk changed the title Cargo feature for WASIp3 Add cfgs to distinguish WASIp3 and WASIp2 targets Sep 9, 2026

@pchickey pchickey left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, just a couple minor tweaks

Comment thread Cargo.toml
Comment thread Cargo.toml Outdated
Comment thread axum/Cargo.toml Outdated
@adamrk

adamrk commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

Thanks, I fixed all that stuff left over from the feature.

@pchickey
pchickey merged commit e4a69a0 into bytecodealliance:main Sep 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants