Fix compatibility warning #169
Open
Conversation
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
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.
The warning was originally introduced because the LLVM upgrade in Rust 1.82 introduces a requirement for reference-types. This is because of a different encoding for the
call_indirectinstruction.However, it turns out that the wasm-opt call actually changes this encoding back to the MVP-compatible one, making the resulting wasm compatible with pre-3.0 versions of CosmWasm. Because of the removal of the
--signext-lowering, we are bounded to 1.3+.We noticed this during a test run at Axelar and I manually tested that this is because of the
wasm-optcall.