[Bug gold/27815] gold fails to build with latest GCC
https://sourceware.org/bugzilla/show_bug.cgi?id=27815 --- Comment #4 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1f1fb219fdc4f96fd967e6173e9090c4c4917e96 commit 1f1fb219fdc4f96fd967e6173e9090c4c4917e96 Author: Alan Modra Date: Thu May 20 08:19:00 2021 +0930 [GOLD] PR27815, gold fails to build with latest GCC ...gold/gc.h:250:37: error: ISO C++ says that these are ambiguous, even though the worst conversion for the first is better than the worst conversion for the second: [-Werror] 250 | (*secvec).push_back(Section_id(NULL, 0)); | ^~~ PR gold/27815 * gc.h (gc_process_relocs): Use nullptr in Section_id constructor. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/25599] gas generates invalid PCREL60B relocation offset with brl.call
https://sourceware.org/bugzilla/show_bug.cgi?id=25599 --- Comment #14 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d71893802fe424e3123ced8c6ed158958487f716 commit d71893802fe424e3123ced8c6ed158958487f716 Author: Alan Modra Date: Sat May 22 12:59:36 2021 +0930 Re: Fix offset for ia64 PCREL60B relocation on HP-UX PR 25599 * config/tc-ia64.c (emit_one_bundle): Expand comment for HP-UX adjustment. Add assertion. * testsuite/gas/ia64/reloc-mlx.d: Pass when slot 2 specified for PCREL60B. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/25599] gas generates invalid PCREL60B relocation offset with brl.call
https://sourceware.org/bugzilla/show_bug.cgi?id=25599 --- Comment #15 from Alan Modra --- Thanks for delving into this, as you can see I've updated the comment and made the testcase accept either slot 1 or 2 for PCREL60B. Interestingly, GNU ld seems to accept either slot 1 or 2 for PCREL60B. At least, the gas/testsuite/gas/ia64/reloc-mlx testcase object with r_offset edited seems to produce the same final linked output as the original, for various --defsym bar=0x. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/27815] gold fails to build with latest GCC
https://sourceware.org/bugzilla/show_bug.cgi?id=27815 Alan Modra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Target Milestone|--- |2.37 Assignee|ccoutant at gmail dot com |amodra at gmail dot com --- Comment #5 from Alan Modra --- Fixed -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/27815] gold fails to build with latest GCC
https://sourceware.org/bugzilla/show_bug.cgi?id=27815 Alan Modra changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Target Milestone|2.37|--- CC||ccoutant at gmail dot com --- Comment #6 from Alan Modra --- Oh oh, maybe I let myself be talked into the nullptr solution when I shouldn't have. The original patch I posted using a cast works everywhere. nullptr, although cleaner, requires c++11, doesn't it? So all versions of gcc prior to 6.1 will need -std=c++11 to be passed to the compiler. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/25599] gas generates invalid PCREL60B relocation offset with brl.call
https://sourceware.org/bugzilla/show_bug.cgi?id=25599 --- Comment #16 from dave.anglin at bell dot net --- Thanks for adjusting the comment. It seems the person that wrote the GNU ld code was aware of the ambiguity. I suspect there will be a need to implement the brl instruction in gcc for GNU Linux at some point, so its good to know that linking with it works. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27871] ld: Add -Bsymbolic-non-weak-functions which only applies to STB_GLOBAL STT_FUNC
https://sourceware.org/bugzilla/show_bug.cgi?id=27871 --- Comment #1 from Fangrui Song --- ld patch: https://sourceware.org/pipermail/binutils/2021-May/116703.html gold patch: https://sourceware.org/pipermail/binutils/2021-May/116683.html (I was considering -Bsymbolic-global-functions but Peter Smith suggested that "global" can confuse users. non-weak or non-vague is better. Detecting vague properly requires detection of COMDAT, which would cause some complexity. I feel that non-weak is better: this way we provide an escape hatch for users who want definition interposition (very rare and good to have a way)) -- You are receiving this mail because: You are on the CC list for the bug.
