Compiling Wasm with Rust 1.70 leads to unsupported Wasm opcodes #1727

webmaster128 · 2023-06-15T09:29:11Z

When compiling a CosmWasm contract with Rust 1.70 (and above?) to Wasm, instructions are emitted that cause the following error:

Wasm bytecode could not be deserialized. Deserialization error: "Unknown opcode 192"

or

Wasm bytecode could not be deserialized. Deserialization error: "Unknown opcode 194"

This referes to C0-C4 in this overview, i.e. the sign extension of Wasm.

See also use-ink/cargo-contract#1139.

Until this resolved, using Rust 1.69.0 is the recommended way. This is also the version used in the latest rust-optimizer/workspace-optimizer.

hashedone · 2023-06-15T10:02:09Z

Also, keep an eye on: rust-lang/rust#109807

aeryz · 2023-06-19T09:06:01Z

We had this issue with the compiler versions 1.70+ but compiling with this command seem to fix it:

RUSTFLAGS='-C target-feature=-sign-ext -C link-arg=-s -C target-cpu=mvp' cargo -Z build-std=std,panic_abort -Z build-std-features=panic_immediate_abort build --release --lib --target wasm32-unknown-unknown

webmaster128 · 2023-06-19T09:32:36Z

I think we just make sure to support the sign extension from 1.3 onwards

mikedotexe · 2023-06-19T22:37:37Z

Since I rarely do toolchain customization, thought I'd drop a comment on how I'm dealing with this. Perhaps saves someone a couple minutes:

rustup install 1.69.0
rustup default 1.69.0

# Then when things are ironed out, set it back
rustup default stable

webmaster128 · 2023-06-20T12:29:25Z

Can you confirm that 1.69.0 works well? I just realized that the current rust-optimizer is on 1.68.2 and not yet 1.69.0. Is it safe to bump it to 1.69.0?

mikedotexe · 2023-06-21T00:25:37Z

Is it safe to bump it to 1.69.0?

Yes, I just double-checked on Juno testnet with a simple contract juno1vll4rksrtkemyvqxmff5a2r9s68px4alqud9wafvzm3m0c5ldm2s2ly243 using the 0.13.0 version from here https://hub.docker.com/layers/cosmwasm/rust-optimizer/0.13.0/images/sha256-2658caa839184c90b93e3ef5d5da0ab091f9e773492faa4b41b30f8973c62651?context=explore

Tested by optimizing, storing, instantiating, doing a contract execution and query, and confirming state changed as I expected.

CosmWasm/cosmwasm#1727

* Add osmosis implementation * Working instantiation * Update instantiation test * Add deposit test * Set rust version to 1.69 CosmWasm/cosmwasm#1727 * Revert "Set rust version to 1.69" This reverts commit 96871d4. * Set toolchain version to 1.69.0 * Add additional deposit test * Add failing test * Fix fmt errors * commit * Add rewards test * Remove summary * Add further tests --------- Co-authored-by: Max <max.grabner@staedter.io>

webmaster128 · 2023-06-26T07:28:14Z

Done in #1743. Will be shipped as part of 1.3.

webmaster128 · 2023-07-22T07:14:11Z

A workaround for CosmWasm < 1.3 is using --signext-lowering in wasm-opt. rust-optimizer does not do that yet but could do so.

Starting from v1.70, Rust uses the Wasm sign extenstion opcodes when comipling to Wasm. Our Wasm parser for static analysis had to be updated in order to correctly parse these opcodes. Refs: - https://github.com/WebAssembly/sign-extension-ops/blob/master/proposals/sign-extension-ops/Overview.md - CosmWasm/cosmwasm#1727 - CosmWasm/cosmwasm#1743

Starting from v1.70, Rust uses the Wasm sign extension opcodes when compiling to Wasm. Our Wasm parser for static analysis had to be updated in order to correctly parse these opcodes. Refs: - CosmWasm/cosmwasm#1727 - CosmWasm/cosmwasm#1743 - https://github.com/WebAssembly/sign-extension-ops/blob/master/proposals/sign-extension-ops/Overview.md

Starting from v1.70, Rust uses the Wasm sign extenstion opcodes when comipling to Wasm. Our Wasm parser for static analysis had to be updated in order to correctly parse these opcodes. Refs: - https://github.com/WebAssembly/sign-extension-ops/blob/master/proposals/sign-extension-ops/Overview.md - CosmWasm/cosmwasm#1727 - CosmWasm/cosmwasm#1743

apollo-sturdy · 2023-09-26T20:10:57Z

I'm still getting this issue when compiling with cargo build --release --lib --target wasm32-unknown-unknown. What's the proper way to deal with this when not using rust-optimizer?

webmaster128 · 2023-09-26T20:18:43Z

What's the proper way to deal with this when not using rust-optimizer?

One of:

Upgrade your chain to wasmd that includes wasmvm 1.3 or 1.4 to support the new instructions
Run .wasm file through wasm-opt with --signext-lowering (e.g. here) to avoid the new instructions

see also: CosmWasm/cosmwasm#1727

* rename states: tokens -> nft_info, contract_info -> collection_info * renamed structs and deprecate: TokenInfo -> NftInfo, ContractInfo -> CollectionInfo, ContractInfoResponse -> CollectionInfoResponse * cargo schema * change storage keys for collection info and nft info, consider in migration and keep legacy data for backward migration * use PA repo for `cw-ownable` * rename generics and make more readable * CollectionInfoResponse -> CollectionInfo * add CollectionInfoExtension with RoyaltyInfo * cargo schema * typo * cleanup * rename * cargo schema * cleanup * creator and owner changes: - new query GetMinterOwnership and GetCreatorOwnership, deprecated Ownership - new execute UpdateMinterOwnership and UpdateCreatorOwnership, deprecate UpdateOwnership - dedicated stores for minter and creator, where creator usess by default cw_ownable singleton! - new migrate msg allowing to reset creator and minter - cleanup migration and split legacy part to dedicated functions - also make sure using decicated CREATOR and MINTER stores and NOT use cw_ownable::... * refactor and move key logic to cw721 package: - move logic from cw721-base to cw721 - merge cw721-base and cw721-metadata-onchain into one, distinction is: `extension: T` where T for base contract is `type DefaultMetadataExtension = Option<Metadata>` - all logic now in default implementation for traits Cw721Execute and Cw721Query * fix ci * cargo fmt * cargo fmt + clippy * cargo fmt * cargo schema * cargo clippy * undo: do not rename token keys * fix unit test * remove useless generic `TMetadataResponse` * remove response structs to msg.rs * cargo schema * move to dedicated fn * docs * rename * cargo clippy * add build script * undo collection info extension and royalty info additions, will be added in next pr * cleanup * generate schemas for entry points, cleanup * update rustc 1.65 -> 1.71 * update cosmwasm version 1.2 -> 1.5, due to rustc compiler issues see also: CosmWasm/cosmwasm#1727 * update optimizer * update rustc 1.71 -> 1.78 * use optimizer * formatting * install rustup first * set $HOME/.cargo/env * install libgcc * install build-base * cleanup * cleanup * Sync cw1155 with upstream (#5) * wip: sync up cw1155 with upstream improvements from cw-awesome * fix build errors/tests --------- Co-authored-by: mr-t <mr-t@arkprotocol.io>

webmaster128 mentioned this issue Jun 19, 2023

Highlight Sign-extension operations in Gatekeeper #1734

Merged

webmaster128 mentioned this issue Jun 19, 2023

Replace parity-wasm with wasmparser for static checks #1735

Closed

nicolaslara mentioned this issue Jun 21, 2023

chore(deps): bump dtolnay/rust-toolchain from 1.69.0 to 1.80.0 osmosis-labs/osmosis#5583

Closed

shapeshed added a commit to InstrumentalFi/instrumental-contracts that referenced this issue Jun 21, 2023

Set rust version to 1.69

96871d4

CosmWasm/cosmwasm#1727

LaurensKubat mentioned this issue Jun 21, 2023

add toolchain.toml quasar-finance/quasar#417

Merged

webmaster128 mentioned this issue Jun 22, 2023

Allow sign extension Wasm opcodes in static validation #1743

Merged

webmaster128 closed this as completed Jun 26, 2023

webmaster128 added this to the 1.3.0 milestone Jun 26, 2023

luca992 mentioned this issue Jun 29, 2023

secret-contract-optimizer: support multiple contracts scrtlabs/SecretNetwork#1471

Merged

RogerKSI mentioned this issue Jul 3, 2023

Compilation failed for Rust 1.70+ bandprotocol/owasm#22

Open

amimart mentioned this issue Jul 31, 2023

Bump rust version to v1.71 axone-protocol/contracts#292

Closed

assafmo mentioned this issue Aug 6, 2023

Support compiling contracts with Rust v1.70+ scrtlabs/SecretNetwork#1500

Merged

jstuczyn mentioned this issue Sep 15, 2023

replaced '--disable-sign-ext' with '--signext-lowering' when running wasm-opt nymtech/nym#3896

Merged

Kayanski mentioned this issue Nov 10, 2023

Unkown opcode error mandrean/cw-optimizoor#41

Closed

MissingNO57 mentioned this issue Nov 30, 2023

chore: Rust optimizer version update to v0.13 fetchai/jenesis#234

Merged

bxq2011hust mentioned this issue May 29, 2024

cargo liquid build 出错 WeBankBlockchain/liquid#42

Closed

taitruong added a commit to arkprotocol/cw-nfts that referenced this issue Jun 13, 2024

update cosmwasm version 1.2 -> 1.5, due to rustc compiler issues

6b3af84

see also: CosmWasm/cosmwasm#1727

seinj0312 added a commit to seinj0312/cw-nft that referenced this issue Jun 30, 2024

update cosmwasm version 1.2 -> 1.5, due to rustc compiler issues

d2f8621

see also: CosmWasm/cosmwasm#1727

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Compiling Wasm with Rust 1.70 leads to unsupported Wasm opcodes #1727

Compiling Wasm with Rust 1.70 leads to unsupported Wasm opcodes #1727

webmaster128 commented Jun 15, 2023

hashedone commented Jun 15, 2023

aeryz commented Jun 19, 2023

webmaster128 commented Jun 19, 2023

mikedotexe commented Jun 19, 2023 •

edited

Loading

webmaster128 commented Jun 20, 2023

mikedotexe commented Jun 21, 2023

webmaster128 commented Jun 26, 2023

webmaster128 commented Jul 22, 2023 •

edited

Loading

apollo-sturdy commented Sep 26, 2023

webmaster128 commented Sep 26, 2023

Compiling Wasm with Rust 1.70 leads to unsupported Wasm opcodes #1727

Compiling Wasm with Rust 1.70 leads to unsupported Wasm opcodes #1727

Comments

webmaster128 commented Jun 15, 2023

hashedone commented Jun 15, 2023

aeryz commented Jun 19, 2023

webmaster128 commented Jun 19, 2023

mikedotexe commented Jun 19, 2023 • edited Loading

webmaster128 commented Jun 20, 2023

mikedotexe commented Jun 21, 2023

webmaster128 commented Jun 26, 2023

webmaster128 commented Jul 22, 2023 • edited Loading

apollo-sturdy commented Sep 26, 2023

webmaster128 commented Sep 26, 2023

mikedotexe commented Jun 19, 2023 •

edited

Loading

webmaster128 commented Jul 22, 2023 •

edited

Loading