https://sourceware.org/bugzilla/show_bug.cgi?id=34846
Bug ID: 34846
Summary: GNU ld misses RISC-V LO12-only local-exec TLS in
shared objects
Product: binutils
Version: 2.46
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: basavesh.shivakumar at wsu dot edu
Target Milestone: ---
Created attachment 17166
--> https://sourceware.org/bugzilla/attachment.cgi?id=17166&action=edit
repro
I'm reporting this bug on behalf of my team: Ananta Srikar Puranam, Emily West,
Dr. Swarn Priya, Dr. Peng Gao and Dr. Basavesh Ammanaghatta Shivakumar.
Summary
=======
GNU ld 2.46 and Binutils master e54e549c26f1 (2.47.50.20261009) accept a RISC-V
shared object whose local-exec TLS reference retains R_RISCV_TPREL_LO12_I but
no TPREL_HI20, emit neither DF_STATIC_TLS nor a dynamic TLS relocation, and
produce a DSO whose dlopen probe reads tp+0 instead of its own tvar; LLD
rejects the same relocation under -shared and the LO12-only object links
normally in a static route.
Reproduction
============
1. Download and extract
`bfd-riscv-tlsle-lo12-in-dso-no-static-tls-reproducer.tar.gz`.
2. Run the following command with an ld.bfd or all-target `ld-new` binary that
supports the emulation used by the reproducer:
LINKERS=/path/to/ld-new sh repro.sh
The archive contains the fixed input files, independent controls, helper
scripts needed by `repro.sh`, and their checksums. The script uses a temporary
directory and does not modify the source tree.
Observed result
===============
GNU ld 2.46 and Binutils master e54e549c26f1 (2.47.50.20261009) accept a RISC-V
shared object whose local-exec TLS reference retains R_RISCV_TPREL_LO12_I but
no TPREL_HI20, emit neither DF_STATIC_TLS nor a dynamic TLS relocation, and
produce a DSO whose dlopen probe reads tp+0 instead of its own tvar; LLD
rejects the same relocation under -shared and the LO12-only object links
normally in a static route.
Expected result
===============
GNU ld should either produce the correct output or reject the input with a
normal diagnostic. It should not crash, hang, execute undefined behavior, read
outside an input-derived allocation, or produce the described malformed
output.
--
You are receiving this mail because:
You are on the CC list for the bug.