rust-lang / rust-lang/rust

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

Open
#132,226 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-discussion O-windows-gnu T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

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 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
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 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the linked StereoKit-rust project, comparing binaries built with rustc 1.81.0 and 1.82.0 on the listed MinGW environments. Use the reported 32-bit pseudo-relocation error and version details to trace the regression; done means the Windows executable launches successfully without that runtime failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.