[Bug binutils/29665] objcopy should display the original name, not a temporary name
https://sourceware.org/bugzilla/show_bug.cgi?id=29665 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |nickc at redhat dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/29655] s390x gas generates PC32DBL instead of PLT32DBL for function call
https://sourceware.org/bugzilla/show_bug.cgi?id=29655
--- Comment #20 from Rui Ueyama ---
GCC 12 seems to always append `@PLT` to a function symbol even if we are not
calling that function. Here is a test case.
```
$ echo 'void foo(); void *bar() { return foo; }' | gcc-12 -S -o- -xc -
.file ""
.machinemode zarch
.machine "z196"
.text
.align 8
.globl bar
.type bar, @function
bar:
.LFB0:
.cfi_startproc
ldgr%f0,%r11
.cfi_register 11, 16
lgr %r11,%r15
.cfi_def_cfa_register 11
larl%r1,foo@PLT
lgr %r2,%r1
lgdr%r11,%f0
.cfi_restore 11
.cfi_def_cfa_register 15
br %r14
.cfi_endproc
.LFE0:
.size bar, .-bar
.ident "GCC: (SUSE Linux) 12.1.1 20220812 [revision
6b7d570a5001bb79e34c0d1626a8c7f55386dac7]"
.section.note.GNU-stack,"",@progbits
```
I think `larl %r1,foo@PLT` should be `larl %r1,foo`.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug gas/29655] s390x gas generates PC32DBL instead of PLT32DBL for function call
https://sourceware.org/bugzilla/show_bug.cgi?id=29655 --- Comment #21 from Andreas Krebbel --- (In reply to Rui Ueyama from comment #20) > GCC 12 seems to always append `@PLT` to a function symbol even if we are not > calling that function. Here is a test case. ... > I think `larl %r1,foo@PLT` should be `larl %r1,foo`. I agree. Ilya is having a look. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29665] objcopy should display the original name, not a temporary name
https://sourceware.org/bugzilla/show_bug.cgi?id=29665 --- Comment #1 from Nick Clifton --- Created attachment 14393 --> https://sourceware.org/bugzilla/attachment.cgi?id=14393&action=edit Proposed patch The problem is that the error message is referring to the (temporary) output file name and not the original input file name. This patch fixes that problem. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29665] objcopy should display the original name, not a temporary name
https://sourceware.org/bugzilla/show_bug.cgi?id=29665 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7fd882d4ad91916fd8a05148117f05ea9f5d756c commit 7fd882d4ad91916fd8a05148117f05ea9f5d756c Author: Nick Clifton Date: Wed Oct 12 15:32:18 2022 +0100 Fix objcopy's error message when it cannot add a .gnu_debuglink section because the section already exists. PR 29665 * objcopy.c (copy_object): Use the input filename when reporting that a .gnu_debuglink section already exists. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29665] objcopy should display the original name, not a temporary name
https://sourceware.org/bugzilla/show_bug.cgi?id=29665 Nick Clifton changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Nick Clifton --- Fixed -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/29655] s390x gas generates PC32DBL instead of PLT32DBL for function call
https://sourceware.org/bugzilla/show_bug.cgi?id=29655 Ilya Leoshkevich changed: What|Removed |Added CC||iii at linux dot ibm.com --- Comment #22 from Ilya Leoshkevich --- Created attachment 14395 --> https://sourceware.org/bugzilla/attachment.cgi?id=14395&action=edit gcc patch -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/29655] s390x gas generates PC32DBL instead of PLT32DBL for function call
https://sourceware.org/bugzilla/show_bug.cgi?id=29655 --- Comment #23 from Ilya Leoshkevich --- I'm currently regtesting the attached patch. This discussion made me realize that our hotpatching support is currently broken in a fashion similar to that of Qt5 (details in the patch's commit message), so I'm shamelessly breaking it even further in order to fix this issue. I will ask Sumanth to double-check my findings, but we will probably have to rework this area. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29677] New: Field `the_bfd` of `asymbol` is uninitialized in function `bfd_mach_o_get_synthetic_symtab`
https://sourceware.org/bugzilla/show_bug.cgi?id=29677 Bug ID: 29677 Summary: Field `the_bfd` of `asymbol` is uninitialized in function `bfd_mach_o_get_synthetic_symtab` Product: binutils Version: 2.40 (HEAD) Status: UNCONFIRMED Severity: critical Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: r3tr0spect2019 at gmail dot com Target Milestone: --- Created attachment 14396 --> https://sourceware.org/bugzilla/attachment.cgi?id=14396&action=edit bug analysis and poc # Reproduce cd binutils-gdb git reset --hard 1d4e62f498b1340569fd58c401f98c287cb5d071 mkdir build ../configure --disable-gdb --disable-gdbserver --disable-gdbsupport --disable-libdecnumber --disable-readline --disable-sim --disable-libbacktrace --disable-gas --disable-ld --disable-werror --enable-targets=all CPPFLAGS=-DDEBUG CFLAGS="-g -O0 -fsanitize=address" make all-binutils MAKEINFO=true && true binutils/objdump -d the_bfd_uninit.bin # Output ../../fuzz/poc/the_bfd_uninit.bin: file format mach-o-x86-64 ./objdump: bfd_mach_o_read_symtab_symbol: symbol "" specified invalid type field 0x6: setting to undefined ./objdump: bfd_mach_o_read_symtab_symbol: symbol "" specified invalid type field 0x4: setting to undefined AddressSanitizer:DEADLYSIGNAL = ==474946==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x55795709e9ec bp 0x7ffd19b7eaf0 sp 0x7ffd19b7eae0 T0) ==474946==The signal is caused by a READ memory access. ==474946==Hint: this fault was caused by a dereference of a high value address (see register values below). Dissassemble the provided pc to learn which register was used. #0 0x55795709e9ec in bfd_get_flavour ../bfd/bfd.h:7803 #1 0x5579570a2b2b in compare_symbols ../../binutils/objdump.c:1204 #2 0x7f3971b6940e in msort_with_tmp stdlib/msort.c:82 #3 0x7f3971b693c1 in msort_with_tmp stdlib/msort.c:44 #4 0x7f3971b693c1 in msort_with_tmp stdlib/msort.c:53 #5 0x7f3971b693a4 in msort_with_tmp stdlib/msort.c:44 #6 0x7f3971b693a4 in msort_with_tmp stdlib/msort.c:52 #7 0x7f3971b693a4 in msort_with_tmp stdlib/msort.c:44 #8 0x7f3971b693a4 in msort_with_tmp stdlib/msort.c:52 #9 0x7f3971b693c1 in msort_with_tmp stdlib/msort.c:44 #10 0x7f3971b693c1 in msort_with_tmp stdlib/msort.c:53 #11 0x7f3971b69a55 in msort_with_tmp stdlib/msort.c:44 #12 0x7f3971b69a55 in __GI___qsort_r stdlib/msort.c:296 #13 0x7f3971da0934 in __interceptor_qsort ../../../../src/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:9917 #14 0x5579570ae4fb in disassemble_section ../../binutils/objdump.c:3780 #15 0x5579575a429f in bfd_map_over_sections ../../bfd/section.c:1373 #16 0x5579570b0855 in disassemble_data ../../binutils/objdump.c:4152 #17 0x5579570b80a3 in dump_bfd ../../binutils/objdump.c:5564 #18 0x5579570b837d in display_object_bfd ../../binutils/objdump.c:5627 #19 0x5579570b86b7 in display_any_bfd ../../binutils/objdump.c:5713 #20 0x5579570b8730 in display_file ../../binutils/objdump.c:5734 #21 0x5579570b9fd1 in main ../../binutils/objdump.c:6130 #22 0x7f3971b4ed8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x7f3971b4ee3f in __libc_start_main_impl ../csu/libc-start.c:392 #24 0x55795709e584 in _start (/home/holing/pro/github/binutils-gdb/build/binutils/objdump+0xdf0584) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV ../bfd/bfd.h:7803 in bfd_get_flavour ==474946==ABORTING Aborted -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29677] Field `the_bfd` of `asymbol` is uninitialized in function `bfd_mach_o_get_synthetic_symtab`
https://sourceware.org/bugzilla/show_bug.cgi?id=29677 2019 changed: What|Removed |Added Build||1d4e62f498b1340569fd58c401f ||98c287cb5d071 Target||objdump -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/29678] Unsupported target for loongrach64-linux-gnu for linker
https://sourceware.org/bugzilla/show_bug.cgi?id=29678 cqwrteur changed: What|Removed |Added Target||loongarch64-linux-gnu Host||x86_64-linux-gnu Build||x86_64-linux-gnu -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/29678] Unsupported target for loongrach64-linux-gnu for linker
https://sourceware.org/bugzilla/show_bug.cgi?id=29678 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com, ||liuzhensong at loongson dot cn -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/29678] New: Unsupported target for loongrach64-linux-gnu for linker
https://sourceware.org/bugzilla/show_bug.cgi?id=29678 Bug ID: 29678 Summary: Unsupported target for loongrach64-linux-gnu for linker Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: euloanty at live dot com CC: ian at airs dot com Target Milestone: --- configure: error: "unsupported target loongarch64-unknown-linux-gnu" make[1]: *** [Makefile:6809: configure-gold] Error 1 make[1]: Leaving directory '/home/cqwrteur/toolchains_build/gcc_build/native/loongarch64-linux-gnu/binutils-gdb' make: *** [Makefile:1004: all] Error 2 -- You are receiving this mail because: You are on the CC list for the bug.
