bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/22533] dynamic relocs generated for weak aliases


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/22533] dynamic relocs generated for weak aliases
Date: Thu, 30 Nov 2017 23:00:23 +0000

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

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

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

commit 4a7e52349807017f9bc09ea25f07924f2ec971b3
Author: Alan Modra <address@hidden>
Date:   Fri Dec 1 07:53:16 2017 +1030

    PR22533, dynamic relocs generated for weak aliases

    This cleans up yet more craziness with non_got_ref.

        PR 22533
        * elf32-hppa.c (elf32_hppa_copy_indirect_symbol): Don't do anything
        special with non_got_ref for weak aliases.
        (elf32_hppa_check_relocs): Tweak setting of non_got_ref.
        (elf32_hppa_adjust_dynamic_symbol): When initialising weak aliases,
        don't uselessly copy non_got_ref.  Clear dyn_relocs instead if
        strong symbol is allocated in dynbss.  Tidy comments.
        (elf32_hppa_relocate_section): Comment fix.
        * elf32-ppc.c (ppc_elf_copy_indirect_symbol): Don't do anything
        special with non_got_ref for weak aliases.
        (ppc_elf_adjust_dynamic_symbol): When initialising weak aliases,
        don't uselessly copy non_got_ref.  Clear dyn_relocs instead if
        strong symbol is allocated in dynbss.  Tidy comments.
        * elf64-ppc.c (ppc64_elf_copy_indirect_symbol): Don't do anything
        special with non_got_ref for weak aliases.
        (ppc64_elf_adjust_dynamic_symbol): When initialising weak aliases,
        don't uselessly copy non_got_ref.  Clear dyn_relocs instead if
        strong symbol is allocated in dynbss.  Tidy comments.

-- 
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]