Skip to content
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

Enable Wasm sign_ext #1189

Merged
merged 5 commits into from
Jul 3, 2023
Merged

Enable Wasm sign_ext #1189

merged 5 commits into from
Jul 3, 2023

Conversation

athei
Copy link
Contributor

@athei athei commented Jul 1, 2023

Fixes #1139

Since Rustc 1.70 we can't disable signed extension anymore. Hence we have to allow it in order to keep functioning. Eventually, we want to remove the parity-wasm dependency but for now we can just enable the sign_ext feature.

Please note that those contracts will not deploy on pallet-contracts, yet. Support is coming soon.

@SkymanOne
Copy link
Contributor

Let's keep the PR open until the support comes so we don't break the master

@athei
Copy link
Contributor Author

athei commented Jul 3, 2023

How would we break master? And which master? The development in this repo is blocked unless you downgrade rustc or merge this PR.

It doesn't break anything. It keeps working if you use rustc < 1.70 and it didn't work with rustc >= 1.70 before. It just to unblock development here.

Copy link
Collaborator

@ascjones ascjones left a comment

Choose a reason for hiding this comment

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

LGTM.

Question is, can/should we add validation to check if a sign_ext is produced and provide a warning (not error)? Even once pallet-contracts is updated, it might be that the target chain is still on an old version.

@athei
Copy link
Contributor Author

athei commented Jul 3, 2023

Yeah we probably should have a warning.

@athei
Copy link
Contributor Author

athei commented Jul 3, 2023

Added a warning if a new rustc is used. I didn't want to scan for the instructions to not add additional dependencies on parity-wasm.

@ascjones ascjones requested a review from a team as a code owner July 3, 2023 08:54
This reverts commit aa2a2e6.
@ascjones
Copy link
Collaborator

ascjones commented Jul 3, 2023

Reverted my CI change because the integration tests fail with CodeRejected. Can update the CI back to stable once substrate-contracts-node is updated to support sign_ext.

@ascjones ascjones merged commit 562ce38 into master Jul 3, 2023
@ascjones ascjones deleted the at/allow-sign-ext branch July 3, 2023 09:56
@ascjones ascjones mentioned this pull request Jul 26, 2023
@ascjones ascjones mentioned this pull request Jul 27, 2023
ascjones added a commit that referenced this pull request Aug 21, 2023
* Enable Wasm sign_ext

* Bump substrate crates

* Add warning when building with new rustc

* Stable toolchain

* Revert "Stable toolchain"

This reverts commit aa2a2e6.

---------

Co-authored-by: Andrew Jones <[email protected]>
ascjones added a commit that referenced this pull request Aug 22, 2023
* Add `SignextLowering` pass to `wasm-opt` (#1280)

* Add `SignextLowering` pass to `wasm-opt`

* Remove check for Rust version

(cherry picked from commit 756aa38)

* Update wasm-opt

* Cargo.lock

* Enable Wasm sign_ext (#1189)

* Enable Wasm sign_ext

* Bump substrate crates

* Add warning when building with new rustc

* Stable toolchain

* Revert "Stable toolchain"

This reverts commit aa2a2e6.

---------

Co-authored-by: Andrew Jones <[email protected]>

* Cargo.lock

* Remove version check

* WIP updating subxt

* Updating subxt

---------

Co-authored-by: Alexander Theißen <[email protected]>
@ascjones ascjones mentioned this pull request Aug 22, 2023
@smiasojed smiasojed mentioned this pull request Mar 4, 2024
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.

Failed to build some contracts with rustc 1.70
3 participants