[Bug binutils/31106] New: strip --strip-debug breaks relocations
https://sourceware.org/bugzilla/show_bug.cgi?id=31106 Bug ID: 31106 Summary: strip --strip-debug breaks relocations Product: binutils Version: 2.41 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: stsp at users dot sourceforge.net Target Milestone: --- Created attachment 15232 --> https://sourceware.org/bugzilla/attachment.cgi?id=15232=edit test case Attached is a test-case. It is an elf file fdppkrnl.35.10.elf with debug info. Please do: ``` $ readelf -r fdppkrnl.35.10.elf | grep ':s8:' | wc -l 65 $ strip --strip-debug fdppkrnl.35.10.elf $ readelf -r fdppkrnl.35.10.elf | grep ':s8:' | wc -l 1 ``` As we can see, strip removed relocations to a particular symbol (1 reloc left from 65). This renders the object disfunctional. llvm-strip works properly and doesn't break anything. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/31105] New: nm -U short flag erroneously consumes argument
https://sourceware.org/bugzilla/show_bug.cgi?id=31105 Bug ID: 31105 Summary: nm -U short flag erroneously consumes argument Product: binutils Version: 2.41 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: fw at immunant dot com Target Milestone: --- `nm` presently (verified in version 2.41.0 from the Arch Linux repository) requires but ignores an argument to the short option `-U` even though this option is documented to be a synonym of the long option `--defined-only`. This regressed in commit https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=aa02037b08312eece5c06e1e98b2ce8b30993c5c which needed to remove the colon after the 'U' in the call to `getopt_long` (L1981), but did not. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30895] gprofng is not relocatable
https://sourceware.org/bugzilla/show_bug.cgi?id=30895 Vladimir Mezentsev changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Vladimir Mezentsev --- Update status as resolved/fixed. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/27215] as: Error: non-constant .uleb128 is not supported on riscv64
https://sourceware.org/bugzilla/show_bug.cgi?id=27215 Fangrui Song changed: What|Removed |Added Resolution|--- |FIXED CC||i at maskray dot me Target Milestone|--- |2.41 Status|UNCONFIRMED |RESOLVED --- Comment #8 from Fangrui Song --- Implemented by https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=f1cd8b94e7c941c2a9107c1112ab2339916b8efd "RISC-V: Support subtraction of .uleb128." in 2023-05 (milestone: binutils 2.41). https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=2029e13917d53d2289d3ebb390c4f40bd2112d21 (2023-10) fixed cases like .word (A + 3) - (B + 2) . GCC debug info probably doesn't emit expressions like this. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/31096] nm for mips32 (native or cross-compiled) shows 32bit addresses as sign-extended 64bit addresses
https://sourceware.org/bugzilla/show_bug.cgi?id=31096 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1 from Nick Clifton --- Hi Nicolas, This is actually expected behaviour. The MIPS architecture uses a signed address space, and tools configured to support the MIPS are aware of this. Hence the mips-linux-gnu-nm tool displays a signed address. Some tools however can be used on architectures for which they were not configured. Nm is one of these tools. So if you use x86_64-linux-gnu-nm on a MIPS binary, it will be able to display the symbols, but it will display their addresses as unsigned values, since that is how the x86_64 architecture treats its addresses. Basically if you want to discover information about MIPS binaries, use tools that are configured to support the MIPS architecture. Note - it is still possible to use cross tools, they just need to support the MIPS. So for example if you build the binutils on an x86_64 host and use the "--enable-targets=all" configure option, then they will be able to correctly handle MIPS binaries, as well as x86_64 binaries and indeed most other architectures as well. Does this make sense ? Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31102] [2.42 Regression] Build property 3 test failures on x86_64-linux-gnux32
https://sourceware.org/bugzilla/show_bug.cgi?id=31102 Matthias Klose changed: What|Removed |Added Summary|[2.42 Regression] pr18841 |[2.42 Regression] Build |test failures on|property 3 test failures on |x86_64-linux-gnux32 |x86_64-linux-gnux32 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31102] [2.42 Regression] pr18841 test failures on x86_64-linux-gnux32
https://sourceware.org/bugzilla/show_bug.cgi?id=31102 Matthias Klose changed: What|Removed |Added CC||hjl.tools at gmail dot com Target||x86_64-linux-gnux32 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31102] New: [2.42 Regression] pr18841 test failures on x86_64-linux-gnux32
https://sourceware.org/bugzilla/show_bug.cgi?id=31102 Bug ID: 31102 Summary: [2.42 Regression] pr18841 test failures on x86_64-linux-gnux32 Product: binutils Version: 2.42 (HEAD) Status: NEW Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org Target Milestone: --- trunk 20231125 fails tests on x86_64-linux-gnux32, succeeding with the 2.41 branch: Test results, compared with installed binutils: W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 3 W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 3 (.o) W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 3 (.so) W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 4 W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 4 (.o) W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 4 (.so) W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 5 W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 5 (.o) W: [ld-x86-64/x86-64.exp] REGRESSION (PASS -> FAIL): Build property 5 (.so) 9 REGRESSIONS (0.18%). 5071 tests: 4961 pass (97.83%), 17 fail (0.34%), 60 xfail (1.18%) 1 untested (0.02%). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31101] [2.42 Regression] nopic link exec test fails on loongarch64-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=31101 Matthias Klose changed: What|Removed |Added Target||loongarch64-linux-gnu -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31101] New: [2.42 Regression] nopic link exec test fails on loongarch64-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=31101 Bug ID: 31101 Summary: [2.42 Regression] nopic link exec test fails on loongarch64-linux-gnu Product: binutils Version: 2.42 (HEAD) Status: NEW Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org Target Milestone: --- 20231125 trunk, nopic link exec test fails on loongarch64-linux-gnu, succeeds with the 2.41 branch: Test results, compared with installed binutils: I: [gas/elf/elf.exp] progression (XFAIL -> PASS): Disabling section padding W: [ld-loongarch-elf/pic.exp] REGRESSION (PASS -> FAIL): nopic link exec test 1 REGRESSIONS (0.04%). 1 progressions (0.04%). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31100] [2.42 Regression] pr18841 test failures on riscv64-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=31100 Matthias Klose changed: What|Removed |Added Target||riscv64-linux-gnu -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31100] New: [2.42 Regression] pr18841 test failures on riscv64-linux-gnu
https://sourceware.org/bugzilla/show_bug.cgi?id=31100 Bug ID: 31100 Summary: [2.42 Regression] pr18841 test failures on riscv64-linux-gnu Product: binutils Version: 2.42 (HEAD) Status: NEW Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org Target Milestone: --- seen with trunk 20231125 on riscv64-linux-gnu. Succeeds with the 2.41 branch: Test results, compared with installed binutils: I: [gas/elf/elf.exp] progression (XFAIL -> PASS): Disabling section padding I: [gas/riscv/riscv.exp] progression (FAIL -> PASS): gas/riscv/zfa W: [ld-ifunc/ifunc.exp] REGRESSION (PASS -> FAIL): Run pr18841 with libpr18841c.so W: [ld-ifunc/ifunc.exp] REGRESSION (PASS -> FAIL): Run pr18841 with libpr18841cn.so (-z now) 2 REGRESSIONS (0.07%). 2 progressions (0.07%). -- You are receiving this mail because: You are on the CC list for the bug.
