[Bug ld/25616] New: --fix-v4bx does not work
https://sourceware.org/bugzilla/show_bug.cgi?id=25616 Bug ID: 25616 Summary: --fix-v4bx does not work Product: binutils Version: 2.31 Status: UNCONFIRMED Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: gary at partis dot co.uk Target Milestone: --- Created attachment 12327 --> https://sourceware.org/bugzilla/attachment.cgi?id=12327&action=edit Tar file containing object and library files to be linked Hi I am using GNU ld version 2.31.1 to target ARMv3 (ARM610/710) processors. Primarily, GCC's libgcc contains "BX LR" instructions which we want changed to "MOV PC,LR" so to be compatible with older processors, but after running the linker with the "--fix-vxb4" directive the BX instructions are still there (we use objdump to disassemble the resultant ELF file to check). Attached is a tar containing some object and library files. They are linked thus : arm-eabi-ld --fix-v4bx -static -nostdlib --format elf32-littlearm --relocatable OS_FuncMain.o StringUtils.o --start-group StringUtils.a ANSIC.a OS.a libgcc.a --end-group -o StringUtils.elf Then a check is made : arm-eabi-objdump StringUtils.elf --disassemble-all --all-headers | grep -i bx ...and the "bx lr" instructions are still there instead of the "mov pc,lr". Kind regards Gary Partis -- You are receiving this mail because: You are on the CC list for the bug.
Issue 19388 in oss-fuzz: binutils:fuzz_disassemble: Segv on unknown address in tic4x_print_register
Updates: Labels: -restrict-view-commit Comment #4 on issue 19388 by sheriffbot: binutils:fuzz_disassemble: Segv on unknown address in tic4x_print_register https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19388#c4 This bug has been fixed for 30 days. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
[Bug gas/25614] dwarf-5 allows for .file 0
https://sourceware.org/bugzilla/show_bug.cgi?id=25614 David Blaikie changed: What|Removed |Added CC||dblaikie at gmail dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/25617] New: Gold looks up shared object information in section headers instead of the dynamic array
https://sourceware.org/bugzilla/show_bug.cgi?id=25617 Bug ID: 25617 Summary: Gold looks up shared object information in section headers instead of the dynamic array Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: klkblake at gmail dot com CC: ian at airs dot com Target Milestone: --- For shared objects, all information needed for linking is in the dynamic array, and section headers are optional. However, gold looks up the information it needs in the (optional) section headers instead of the (mandatory) dynamic array, and fails if the section headers are not present. As a result, gold is unable to link to shared objects with no section headers, even though such shared objects are spec-compliant and the dynamic linker can load them without issue. This is unfortunate, as working around it requires redundantly respecifying most of the dynamic array in section headers. This seems like it should not be too hard to fix, from what I've seen of gold's shared object handling, but I'm not particularly familiar with the codebase so I don't know if there are things I'm missing. The BFD-based linker also exhibits this issue. -- You are receiving this mail because: You are on the CC list for the bug.
