bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/16744] '-z noexecstack' does not add .note.GNU-stack for relocat


From: cvs-commit at gcc dot gnu.org
Subject: [Bug ld/16744] '-z noexecstack' does not add .note.GNU-stack for relocatables
Date: Mon, 31 Mar 2014 12:17:45 +0000

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

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  76f0cad6f4e0fdfc4cfeee135b44b6a090919c60 (commit)
      from  72c56015dda568cdcce75dc0316aa768f922c2d7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

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

commit 76f0cad6f4e0fdfc4cfeee135b44b6a090919c60
Author: Nick Clifton <address@hidden>
Date:   Mon Mar 31 13:14:44 2014 +0100

    This is a fix for PR ld/16744 which showed that an object file linked with
-r and -z [no]execstack
    would not honour the [no]execstack.  Fully linked binaries use a special
segment to indicate the
    state of the stack, but relocatable object files only have sections, and
.note.GNU-stack was not
    being created.

        * emultempl/elf32.em (_after_open): Create a .note.GNU-stack
        section when performing a relocatable link with -z [no]execstack
        specified.

-----------------------------------------------------------------------

Summary of changes:
 ld/ChangeLog          |    7 +++++++
 ld/emultempl/elf32.em |   15 ++++++++++++++-
 2 files changed, 21 insertions(+), 1 deletions(-)

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