bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/23189] bad symbol index: ffffffff


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/23189] bad symbol index: ffffffff
Date: Mon, 21 May 2018 15:49:35 +0000

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

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The binutils-2_30-branch branch has been updated by H.J. Lu
<address@hidden>:

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

commit 19dd615652084b2bfd81a0497864e193608037a0
Author: H.J. Lu <address@hidden>
Date:   Fri May 18 06:43:19 2018 -0700

    x86: Don't set eh->local_ref to 1 for linker defined symbols

    Since symbols created by HIDDEN and PROVIDE_HIDDEN assignments in
    linker script may be marked as defined, but not hidden, we can't
    set eh->local_ref to 1 in _bfd_x86_elf_link_symbol_references_local.

    Also R_386_GOT32X should be handled as just like R_386_GOT32 when
    relocating a section.  The input R_386_GOT32X relocations, which
    can be relaxed, should have been converted to R_386_PC32, R_386_32
    or R_386_GOTOFF.

    bfd/

        PR ld/23189
        * elf32-i386.c (elf_i386_relocate_section): Handle R_386_GOT32X
        like R_386_GOT32.
        * elfxx-x86.c (_bfd_x86_elf_link_symbol_references_local): Don't
        set eh->local_ref to 1 for linker defined symbols.

    ld/

        PR ld/23189
        * testsuite/ld-i386/i386.exp: Run pr23189.
        * testsuite/ld-x86-64/x86-64.exp: Likewise.
        * testsuite/ld-i386/pr23189.d: New file.
        * testsuite/ld-i386/pr23189.s: Likewise.
        * testsuite/ld-i386/pr23189.t: Likewise.
        * testsuite/ld-x86-64/pr23189.d: Likewise.
        * testsuite/ld-x86-64/pr23189.s: Likewise.
        * testsuite/ld-x86-64/pr23189.t: Likewise.

    (cherry picked from commit 011b32fd4270fb7111ee1f63695ccd44562ee7df)

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]