[Bug binutils/25651] objcopy : SIGSEGV in copy_object ( objcopy.c:3392 )
https://sourceware.org/bugzilla/show_bug.cgi?id=25651 Alan Modra changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #1 from Alan Modra --- Fixed with commit 9cc89dc0acc1 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/25611] [DWARF-5] support for checksums in .file directives
https://sourceware.org/bugzilla/show_bug.cgi?id=25611 Nick Clifton changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Nick Clifton --- Support for this feature has now been added to the assembler: commit 5496f3c635 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/25614] dwarf-5 allows for .file 0
https://sourceware.org/bugzilla/show_bug.cgi?id=25614 --- Comment #11 from Nick Clifton --- Hi Nick, Right - I have now checked in a patch which should provide full support for the ".file 0" directive. Plus it handles .file "dir" "file" md5 as well. One question - what is the .addrsig directive ? It is in the foo.s file that you uploaded (near the end) but gas does not recognise it. Also - please can you check to see if the patched assembler now provides the functionality that you need ? Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/25614] dwarf-5 allows for .file 0
https://sourceware.org/bugzilla/show_bug.cgi?id=25614 --- Comment #12 from David Blaikie --- (In reply to Nick Clifton from comment #11) > Hi Nick, > > Right - I have now checked in a patch which should provide full support for > the ".file 0" directive. Plus it handles .file "dir" "file" md5 as > well. > > One question - what is the .addrsig directive ? It is in the foo.s file > that you uploaded (near the end) but gas does not recognise it. Here's the documentation for the addrsig LLVM extension: https://llvm.org/docs/Extensions.html#sht-llvm-addrsig-section-address-significance-table -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/24920] Executable produces nonsensical error message after statically linking with trying to link in a dynamic library.
https://sourceware.org/bugzilla/show_bug.cgi?id=24920 --- Comment #3 from Geir Johansen --- Problem still occurs with somewhat more recent software: $ gcc --version gcc (GCC) 9.2.0 20190812 (Cray Inc.) Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ gcc -c hello.c $ ld --version GNU ld (GNU Binutils) 2.32 Copyright (C) 2019 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) a later version. This program has absolutely no warranty. $ ld -m elf_x86_64 -static /usr/lib64/crt1.o /usr/lib64/crti.o /opt/gcc/9.2.0/snos/lib/gcc/x86_64-suse-linux/9.2.0/crtbeginT.o -L/opt/gcc/9.2.0/snos/lib/gcc/x86_64-suse-linux/9.2.0 -L/opt/gcc/9.2.0/snos/lib/lib64 hello.o --start-group -lgcc -lgcc_eh -lc --end-group /opt/gcc/9.2.0/snos/lib/gcc/x86_64-suse-linux/9.2.0/crtend.o /usr/lib64/crtn.o -Bdynamic /lib64/libaio.so.1 $ ./a.out -bash: ./a.out: No such file or directory $ file a.out a.out: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld6, for GNU/Linux 3.2.0, with debug_info, not stripped $ ldd a.out linux-vdso.so.1 (0x7ffc5a318000) libaio.so.1 => /lib64/libaio.so.1 (0x7f1372c2c000) libc.so.6 => /lib64/libc.so.6 (0x7f1372872000) /lib/ld64.so.1 => /lib64/ld-linux-x86-64.so.2 (0x7f1372e2e000) $ -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/24920] Executable produces nonsensical error message after statically linking with trying to link in a dynamic library.
https://sourceware.org/bugzilla/show_bug.cgi?id=24920 --- Comment #4 from H.J. Lu --- (In reply to Geir Johansen from comment #3) > Problem still occurs with somewhat more recent software: > It is interaction between "gcc -static" and linker -static/-Bdynamic. When -static is passed to gcc, gcc passes it to linker to create static binary. -Bdynamic cancels -static passed from gcc. But gcc only provides linker options to create static executable, not dynamic executable. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/24905] X86 PCREL relocation against hidden symbol defined in linker scripts fails
https://sourceware.org/bugzilla/show_bug.cgi?id=24905 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |2.34 --- Comment #3 from H.J. Lu --- Fixed for 2.34. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/24920] Executable produces nonsensical error message after statically linking with trying to link in a dynamic library.
https://sourceware.org/bugzilla/show_bug.cgi?id=24920 --- Comment #5 from H.J. Lu --- Created attachment 12366 --> https://sourceware.org/bugzilla/attachment.cgi?id=12366&action=edit Try this -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/24920] Executable produces nonsensical error message after statically linking with trying to link in a dynamic library.
https://sourceware.org/bugzilla/show_bug.cgi?id=24920 H.J. Lu changed: What|Removed |Added Attachment #12366|0 |1 is obsolete|| -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/24920] Executable produces nonsensical error message after statically linking with trying to link in a dynamic library.
https://sourceware.org/bugzilla/show_bug.cgi?id=24920 H.J. Lu changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW URL||https://sourceware.org/pipe ||rmail/binutils/2020-March/1 ||10196.html Last reconfirmed||2020-03-11 Target Milestone|--- |2.35 --- Comment #6 from H.J. Lu --- A patch is posted at https://sourceware.org/pipermail/binutils/2020-March/110196.html -- You are receiving this mail because: You are on the CC list for the bug.
