Compiling tests for wasm64-unknown-unknown on latest Nightly results in linking error
#121460
Labels
-Zbuild-std
Unstable Cargo option: Compile the standard library yourself.
A-linkage
Area: linking into static, shared libraries and binaries
C-bug
Category: This is a bug.
O-wasm
Target: WASM (WebAssembly), http://webassembly.org/
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
rustbot
added
the
needs-triage
|
Probably related to #120588 cc @alexcrichton |
|
Yep definitely looks like my fault, I'll work on a fix! |
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Feb 22, 2024
It looks like LLD will detect object files being either 32 or 64-bit depending on any memory present. LLD will additionally reject 32-bit objects during a 64-bit link. Previously metadata objects did not have any memories in them which led LLD to conclude they were 32-bit objects which broke 64-bit targets for wasm. This commit fixes this by ensuring that for 64-bit targets there's a memory object present to get LLD to detect it's a 64-bit target. Additionally this commit moves away from a hand-crafted wasm encoder to the `wasm-encoder` crate on crates.io as the complexity grows for the generated object file. Closes rust-lang#121460
jieyouxu
added
A-linkage
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Feb 29, 2024
…iser rustc: Fix wasm64 metadata object files It looks like LLD will detect object files being either 32 or 64-bit depending on any memory present. LLD will additionally reject 32-bit objects during a 64-bit link. Previously metadata objects did not have any memories in them which led LLD to conclude they were 32-bit objects which broke 64-bit targets for wasm. This commit fixes this by ensuring that for 64-bit targets there's a memory object present to get LLD to detect it's a 64-bit target. Additionally this commit moves away from a hand-crafted wasm encoder to the `wasm-encoder` crate on crates.io as the complexity grows for the generated object file. Closes rust-lang#121460
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 1, 2024
Rollup merge of rust-lang#121464 - alexcrichton:fix-wasm64, r=wesleywiser rustc: Fix wasm64 metadata object files It looks like LLD will detect object files being either 32 or 64-bit depending on any memory present. LLD will additionally reject 32-bit objects during a 64-bit link. Previously metadata objects did not have any memories in them which led LLD to conclude they were 32-bit objects which broke 64-bit targets for wasm. This commit fixes this by ensuring that for 64-bit targets there's a memory object present to get LLD to detect it's a 64-bit target. Additionally this commit moves away from a hand-crafted wasm encoder to the `wasm-encoder` crate on crates.io as the complexity grows for the generated object file. Closes rust-lang#121460
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiling any crate with
cargo test --no-run -Z build-std=std,panic_abort --target=wasm64-unknown-unknownresults in the following error:rust-lld: error: /home/dir/.cargo/target/wasm64-unknown-unknown/debug/deps/libtest-ed35d2d81ad088d3.rlib(lib.rmeta): wasm32 object file can't be linked in wasm64 mode. This is a regression introduced in one of the recent NIghtly versions.Toolchain version: cargo 1.78.0-nightly (194a60b29 2024-02-21)
The text was updated successfully, but these errors were encountered: