Upgrading from 1.81 to 1.82 create unconsistent exe file (Release only): Mingw-w64 runtime failure: 32 bit pseudo relocation

[mvvvv]

About my project https://github.com/mvvvv/StereoKit-rust I was able to create from linux (mingw 13 & 14.2) and windows (MSYS 14.2) a working windows-exe binary created with gcc.

after update to 1.82 I systematically have the following error when launching the windows-exe (windows11-pro or wine):
Mingw-w64 runtime failure: 32 bit pseudo relocation at 00000001400017D9 out of range, targeting 00006FFFFAEF8E90, yielding the value 00006FFEBAEF76B3.

It most recently worked on:

rustc 1.81.0 (eeb90cd 2024-09-04)
binary: rustc
commit-hash: eeb90cd
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7

Version with regression

rustc 1.82.0 (f6e511e 2024-10-15)
binary: rustc
commit-hash: f6e511e
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1

Backtrace

Nothing more

@rustbot modify labels: +regression-from-stable-to-stable -regression-untriaged

[mvvvv]

Same error with nightly

rustc 1.84.0-nightly (9b18a12 2024-10-26)
binary: rustc
commit-hash: 9b18a12
commit-date: 2024-10-26
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1

mv@mv-R8700F:~/dvlt/sk_builds/SK_demo_win_gnu$ wine main_pc.exe
Mingw-w64 runtime failure:
32 bit pseudo relocation at 00000001400017D9 out of range, targeting 00006FFFFAEF8E90, yielding the value 00006FFEBAEF76B3.

[jieyouxu]

StereoKit's build.rs looks quite complicated with a lot of linker-related settings, is there anything smaller that can reproduce this? I imagine bisecting this is also going to be difficult...

[mvvvv]

Sorry, I only have this build.rs. I tried with a basic hello world test without having the problem.

[mati865]

A couple of questions that can help to narrow down the problem.
This looks like you are building a 64-bit binary, is that correct?
Can you try with LLD? Assuming you have LLD in your PATH, you just need to pass -Clink-arg=-fuse-ld=lld either to the build script or the compiler (with RUSTFLAGS) depending where the problem is. This looks a lot like https://reviews.llvm.org/D118328
Can you try with --disable-runtime-pseudo-reloc and also with --disable-auto-import? It will likely fail but could tell which symbols needed relocations (though I worry there will be a lot of them).

[mvvvv]

Not sure to know how to do what you're asking for:

RUSTFLAGS="-C link-arg=-fuse-ld=lld --disable-auto-import" cargo build_sk_rs --x64-win-gnu ../x64-mingw-libs/ --example main_pc --features event-loop ../sk_builds/SK_demo_win_gnu/

error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/mv/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names -C link-arg=-fuse-ld=lld --disable-auto-import --target x86_64-pc-windows-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Unrecognized option: 'disable-auto-import'


thread 'main' panicked at src/bin/cargo-build_sk_rs.rs:181:9:
cargo build failed!
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace```

[mvvvv]

And it's 64 bits.