bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/22423] PT_PHDR segment is marked with PF_X


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/22423] PT_PHDR segment is marked with PF_X
Date: Mon, 13 Nov 2017 01:06:43 +0000

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

--- Comment #3 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=f882209d9aa5b68d68c45c5849e129ffc228749c

commit f882209d9aa5b68d68c45c5849e129ffc228749c
Author: H.J. Lu <address@hidden>
Date:   Sun Nov 12 17:03:50 2017 -0800

    ld: Remove PF_X from PT_PHDR segment

    It was reasonable to mark PT_PHDR segment with PF_X for compatibility
    with UnixWare and Solaris linkers 20 years ago.  But it is inappropriate
    today when the primary OS of GNU ld is Linux.  This patch removes PF_X
    from PT_PHDR segment as gold does.

    Tested natively on Linux/x86 as well as crosss-binutils for alpha-linux,
    ia64-linux, powerpc64-linux, powerpc-linux, s390-linux, s390x-linux,
    sparc64-linux and sparc-linux.

    bfd/

        PR ld/22423
        * elf.c (_bfd_elf_map_sections_to_segments): Remove PF_X from
        PT_PHDR segment.

    ld/

        PR ld/22423
        * testsuite/ld-alpha/tlsbin.rd: Replace "R E " with "R +" for
        PT_PHDR segment.
        * testsuite/ld-alpha/tlsbinr.rd: Likewise.
        * testsuite/ld-ia64/tlsbin.rd: Likewise.
        * testsuite/ld-powerpc/tlsexe.r: Likewise.
        * testsuite/ld-powerpc/tlsexe32.r: Likewise.
        * testsuite/ld-powerpc/tlsexetoc.r: Likewise.
        * testsuite/ld-s390/tlsbin.rd: Likewise.
        * testsuite/ld-s390/tlsbin_64.rd: Likewise.
        * testsuite/ld-sparc/tlssunbin32.rd: Likewise.
        * testsuite/ld-sparc/tlssunbin64.rd: Likewise.
        * testsuite/ld-elf/pr22423.d: New test.

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