Skip to content

Spurious linker error with armv7-unknown-linux-gnueabihf-gcc: relocation truncated to fit: R_ARM_THM_JUMP24 against symbol #49845

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
alexcrichton opened this issue Apr 10, 2018 · 2 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@alexcrichton
Copy link
Member

First seen at #49809 (comment) I feel like I've seen this before but don't recall the circumstances. In any case, opening a tracking issue so we can collect this and see it happening!

@alexcrichton alexcrichton added O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) labels Apr 10, 2018
@XAMPPRocky XAMPPRocky added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC labels Jul 7, 2018
@kennytm kennytm changed the title Spurious failure in the linker on ARM Spurious linker error with armv7-unknown-linux-gnueabihf-gcc: relocation truncated to fit: R_ARM_THM_JUMP24 against symbol Oct 18, 2018
@kennytm
Copy link
Member

kennytm commented Oct 18, 2018

Edited title to make it easier to find.

All known instances so far:

  1. Add filtering options to rustc_on_unimplemented #47613 (comment) (2018-02-07T14:54:12Z)
  2. Stop emitting color codes on TERM=dumb #49809 (comment) (2018-04-10T12:58:22Z)
  3. lint reasons (RFC 2383, part 1) #54683 (comment) (2018-10-17T05:26:24Z)
  4. Add tracking issue for Layout methods (and some API changes) #55366 (comment) (2018-11-07T03:20:12Z)

The first link suggests this is caused by https://sourceware.org/bugzilla/show_bug.cgi?id=20608.

@pnkfelix
Copy link
Member

pnkfelix commented Jun 3, 2022

visiting for T-compiler backlog bonanza. It seems like this (very specific?) issue hasn't occurred since 2018.

So I'm going to close this. but please reopen if you have evidence of a recent instance of this occurring.

@pnkfelix pnkfelix closed this as completed Jun 3, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants