[Bug ld/28264] [2.37 Regression] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 --- Comment #5 from Alan Modra --- At least, that would get us back to the 2.35 behaviour of compiling your #c3 testcase without complaint if not using -flto, and complaining about multiple definitions of _efi_set_variable if using -flto. --

[Bug ld/28264] [2.37 Regression] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 --- Comment #4 from Alan Modra --- (In reply to H.J. Lu from comment #2) > calls _bfd_generic_link_add_one_symbol with string == NULL. Yes, it looks like commit 726d7d1ecfd1fc should have checked for that in the MIND case before calling strcm

[Bug ld/28264] [2.37 Regression] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 --- Comment #3 from H.J. Lu --- [hjl@gnu-cfl-2 pr28264]$ cat foo.v libefivar.so.0 { global: _efi_set_variable; local: *; }; [hjl@gnu-cfl-2 pr28264]$ cat foo.c void __attribute__ ((symver ("_efi_set_varia...@li

[Bug ld/28264] [2.37 Regression] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 --- Comment #2 from H.J. Lu --- (gdb) f 1 #1 0x0043b9b4 in _bfd_generic_link_add_one_symbol ( info=0x667620 , abfd=0x6d9240, name=0xa756d2 "_efi_set_variable", flags=2, section=0xa661e8, value=29806, string=0x0, copy=fal

[Bug gas/28266] New: CWD present in object file even after use of -fdebug-prefix-map=$PWD=foo

2021-08-25 Thread joel at rosdahl dot net
https://sourceware.org/bugzilla/show_bug.cgi?id=28266 Bug ID: 28266 Summary: CWD present in object file even after use of -fdebug-prefix-map=$PWD=foo Product: binutils Version: 2.38 (HEAD) Status: UNCONFIRMED Se

[Bug binutils/21409] objdump segfault - null pointer dereferencing

2021-08-25 Thread ovilewade9 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21409 ovile009988 changed: What|Removed |Added CC||ovilewade9 at gmail dot com --- Comment

[Bug ld/28264] [2.37 Regression] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 H.J. Lu changed: What|Removed |Added CC||hjl.tools at gmail dot com -- You are rece

[Bug ld/28264] [2.37 Regression] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 H.J. Lu changed: What|Removed |Added Summary|ld.bfd crashes on linking |[2.37 Regression] ld.bfd

[Bug ld/28264] ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 H.J. Lu changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug ld/26978] Inconsistency for defined foo@v1 and foo@@v1

2021-08-25 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=26978 H.J. Lu changed: What|Removed |Added See Also||https://sourceware.org/bugz

[Bug gas/28078] arm: fails to build when using armv8 neon with dotprod extension

2021-08-25 Thread happyalu at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28078 --- Comment #7 from Alok Parlikar --- Thank you so much! I've also posted this status on the xnnpack issue that motivated this issue report. https://github.com/google/XNNPACK/issues/1465 -- You are receiving this mail because: You are on the

[Bug ld/28264] New: ld.bfd crashes on linking efivar with LTO

2021-08-25 Thread kloczko.tomasz at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28264 Bug ID: 28264 Summary: ld.bfd crashes on linking efivar with LTO Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Comp

[Bug gas/28078] arm: fails to build when using armv8 neon with dotprod extension

2021-08-25 Thread rearnsha at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=28078 --- Comment #6 from Richard Earnshaw --- For completeness, GCC has now been fixed on master and all maintained releases (back to gcc-9). -- You are receiving this mail because: You are on the CC list for the bug.