https://sourceware.org/bugzilla/show_bug.cgi?id=10957

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by Alan Modra <amo...@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=02d2a36902c7b0fefe05e8d9bdbf11e846ac71fe

commit 02d2a36902c7b0fefe05e8d9bdbf11e846ac71fe
Author: Alan Modra <amo...@gmail.com>
Date:   Sat Jul 15 19:47:10 2023 +0930

    PR10957, Missing option to really print section+offset

    Many of the reloc error messages have already been converted from
    using %C to using %H in ld.bfd, to print section+offset as well as
    file/line/function.  This catches a few remaining, and changes gold to
    do the same.

            PR 10957
    bfd/
            * elf32-sh.c (sh_elf_relocate_section): Use %H in error messages.
    gold/
            * object.cc (Relocate_info::location): Always report
section+offset.
            * testsuite/debug_msg.sh: Adjust to suit.
            * testsuite/x32_overflow_pc32.sh: Likewise.
            * testsuite/x86_64_overflow_pc32.sh: Likewise.
    ld/
            * emultempl/pe.em (read_addend): Use %H in error message.
            * emultempl/pep.em (read_addend): Likewise.
            * ldcref.c (check_reloc_refs): Likewise.
            * ldmain.c (warning_find_reloc, undefined_symbol): Likewise.
            * pe-dll.c (pe_create_import_fixup): Likewise.
            * testsuite/ld-cris/undef2.d: Adjust expected output to suit.
            * testsuite/ld-cris/undef3.d: Likewise.
            * testsuite/ld-elf/shared.exp: Likewise.
            * testsuite/ld-i386/compressed1.d: Likewise.
            * testsuite/ld-ia64/line.exp: Likewise.
            * testsuite/ld-plugin/lto.exp: Likewise.
            * testsuite/ld-undefined/undefined.exp: Likewise.
            * testsuite/ld-x86-64/compressed1.d: Likewise.
            * testsuite/ld-x86-64/line.exp: Likewise.
            * testsuite/ld-x86-64/pr27587.err: Likewise.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to