https://sourceware.org/bugzilla/show_bug.cgi?id=34179
Bug ID: 34179
Summary: [RISC-V ld] wrap after partial link keeps stale foo
value
Product: binutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: l784896635 at gmail dot com
Target Milestone: ---
During RISC-V linker regression/conformance testing, I reduced this
linker-stage issue.
## Actual behavior
After a.o and b.o are partially linked with ld -r, GNU ld.bfd leaves _start
calling foo directly in the final --wrap=foo link, while ld.lld on the same
ab.o + w.o input redirects _start to __wrap_foo.
## Expected behavior
The linker should produce the semantically correct RISC-V output for this
reduced testcase, or issue a controlled diagnostic when the input is outside
the supported semantics. It should not silently emit a wrong output, lose
required metadata/relocations/attributes, miss a required relaxation, report a
false range/non-PIC/non-convergence error, or crash.
## Test input and intent
A final link applies --wrap=foo after a prior ld -r step that combined the
caller and the original foo definition. The wrapped call from _start should
still be redirected to __wrap_foo.
## Target and route
- Target tracker: GNU binutils / ld
- Target ISA / ABI: `rv64imac` / `lp64`
- First failing stage: link
- Toolchain route used in reduction: gas+ld.bfd with gas+ld.lld control
## Reproduction evidence
3 clean reproductions in packaged run1..run3 evidence show stable ld.bfd output
with _start: jal foo and ld.lld control output with _start: jal __wrap_foo from
the same partially linked ab.o input.
The reproducer bundle contains the reduced testcase plus three local
reproduction runs. The evidence is text-only: linker outputs, disassembly,
relocation dumps, symbol dumps, and short summaries where available.
Reproducer bundle:
https://github.com/anonymous25989/riscv-linker-48-reproducers/raw/main/r48-v2/attachments/gnu_008_wrap_after_partial_link_keeps_stale_foo_value_reproducer.zip
## Notes
This is reported as a linker-stage behavior defect found during RISC-V linker
regression/conformance testing. The reduced testcase is intentionally small so
that the failure mode is easy to inspect. The attached evidence is already
reproduced; no additional local path or private workspace is required.
--
You are receiving this mail because:
You are on the CC list for the bug.
