bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/23515] Empty GNU_PROPERTY_X86_FEATURE_1_AND isn't removed


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/23515] Empty GNU_PROPERTY_X86_FEATURE_1_AND isn't removed
Date: Fri, 17 Aug 2018 10:56:03 +0000

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

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

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

commit bfb1e8c15a6b7d02cd0b9a124d01722a07ebf09a
Author: H.J. Lu <address@hidden>
Date:   Fri Aug 17 03:54:05 2018 -0700

    x86: Remove empty X86_FEATURE_1_AND property

    There is no need to generate .note.gnu.property section with empty
    X86_FEATURE_1_AND property.  This patch adds fixup_gnu_properties
    to ELF linker backend so that x86 backend can remove it.

    bfd/

        PR ld/23515
        * elf-bfd.h (elf_backend_data): Add fixup_gnu_properties.
        * elf-properties.c (_bfd_elf_link_setup_gnu_properties): Call
        backend fixup_gnu_properties if it isn't NULL.  Discard
        .note.gnu.property section if all properties have been removed.
        * elfxx-target.h (elf_backend_fixup_gnu_properties): New.
        (elfNN_bed): Initialize fixup_gnu_properties.
        * elfxx-x86.c (_bfd_x86_elf_link_fixup_gnu_properties): New
        function.
        * elfxx-x86.h (_bfd_x86_elf_link_fixup_gnu_properties): New
        prototype.
        (elf_backend_fixup_gnu_properties): New.

    ld/

        PR ld/23515
        * testsuite/ld-i386/ibt-plt-2a.d: Updated.
        * testsuite/ld-i386/ibt-plt-2b.d: Likewise.
        * testsuite/ld-x86-64/ibt-plt-2a-x32.d: Likewise.
        * testsuite/ld-x86-64/ibt-plt-2a.d: Likewise.
        * testsuite/ld-x86-64/ibt-plt-2b-x32.d: Likewise.
        * testsuite/ld-x86-64/ibt-plt-2b.d: Likewise.

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