Update Rust toolchain to 1.93.1 and add wasm32-linera-chain target#5646
Draft
deuszx wants to merge 13 commits intotestnet_conwayfrom
Draft
Update Rust toolchain to 1.93.1 and add wasm32-linera-chain target#5646deuszx wants to merge 13 commits intotestnet_conwayfrom
deuszx wants to merge 13 commits intotestnet_conwayfrom
Conversation
Contributor
|
We really should work on |
deuszx
force-pushed
the
rust-1.93-toolchain
branch
4 times, most recently
from
44c1fe0 to
2b701d6
Compare
Closed
Bump stable toolchain to 1.93.1 and nightly to nightly-2026-03-01. Introduce a custom wasm32-linera-chain target that disables bulk-memory and nontrapping-fptoint opcodes (0xFC prefix) for on-chain Wasm applications. Update wasmer/wasm-instrument to git forks with probestack and bulk-memory support, unpin ruzstd, and remove bridge-e2e MSRV workarounds that are no longer needed. Add the target spec and cargo config to the project template so that `linera project new` produces projects ready to build for the chain target. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The 4 changes: 1. linera-witty-macros/src/wit_interface.rs:205 — **return_type = actual_output (avoid needless Box allocation) 2. linera-witty/src/runtime/wasmer/mod.rs:126 — StoreMut<'_> (explicit elided lifetime) 3. linera-witty/src/runtime/wasmtime/mod.rs:44 — StoreContext<'_, UserData> 4. linera-witty/src/runtime/wasmtime/mod.rs:50 — StoreContextMut<'_, UserData>
deuszx
force-pushed
the
rust-1.93-toolchain
branch
from
3a49676 to
a34257b
Compare
Twey
reviewed
Mar 10, 2026
Comment on lines
+69
to
+71
| - name: Install nightly toolchain for wasm builds | ||
| run: | | ||
| rustup toolchain install $(sed -n 's/^channel = "\(.*\)"/\1/p' toolchains/nightly/rust-toolchain.toml) --component rust-src |
Contributor
There was a problem hiding this comment.
I don't love parsing TOML with sed 😅 We do this generally by linking the toolchain to rust-toolchain.toml.
I wonder if it's time to always use a nightly toolchain. We can still be compatible with stable Rust by forbidding #![feature] flags in the core code — @ma2bd for interest.
Twey
reviewed
Mar 10, 2026
| unset RUSTUP_TOOLCHAIN RUSTFLAGS | ||
| cd examples | ||
| cargo build --locked --release --target wasm32-unknown-unknown | ||
| cargo build --locked --release --target wasm32-linera-chain |
Contributor
There was a problem hiding this comment.
We can (and should) put this in .cargo/config.toml so we don't need to specify it here.
Contributor
Author
There was a problem hiding this comment.
IIRC, the issue was that .cargo/config.toml was being ignored in the CI b/c of some ENV overwrites.
Contributor
There was a problem hiding this comment.
I think its RUSTFLAGS specifically are a bit fiddly. But the target should be fine.
Twey
reviewed
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Right now we're stuck on a quite old 1.88 toolchain. This is increasing becoming a problem when certain dependencies have version conflicts that are hard to resolve or only possible to resolve on newer toolchains.
Proposal
wasm32-linera-chaintarget that disables bulk-memory and nontrapping-fptoint opcodes (0xFC prefix) for on-chain Wasm applications.wasmer/wasm-instrumentto git forks with probestack and bulk-memory supportlinera project newproduces projects ready to build for the chain target.Test Plan
CI
Release Plan
Links