You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the fact that a contract can currently only support a maximum of 2^32 bytes of data, we should allow piecrust-uplink to build properly for the wasm64-unknown-unknown target. This will enlarge the address space significantly, and then it will become the job of piecrust support such large memories.
Possible solution design or implementation
Since wasm64-unknown-unknown is a tier 3 target, the implementer will have to build the Rust compiler from source. They will therefore also have to choose how this compiler is disseminated to developers and contract builders alike.
The text was updated successfully, but these errors were encountered:
The compiler is downloaded and extracted to the target directory, and
linked to the toolchains in the rustup directory, making it available to
be used anyone in the system.
The compiler is available as under the `+dusk` option in rust tools, and
is able to compile at least the `wasm32-unknown-unknown` target.
See-also: #280
Summary
Given the fact that a contract can currently only support a maximum of 2^32 bytes of data, we should allow
piecrust-uplink
to build properly for thewasm64-unknown-unknown
target. This will enlarge the address space significantly, and then it will become the job ofpiecrust
support such large memories.Possible solution design or implementation
Since
wasm64-unknown-unknown
is a tier 3 target, the implementer will have to build the Rust compiler from source. They will therefore also have to choose how this compiler is disseminated to developers and contract builders alike.The text was updated successfully, but these errors were encountered: