From: Nick Clifton <nickc@redhat.com>
To: "Jeff Law" <jeffreyalaw@gmail.com>, "Martin Liška" <mliska@suse.cz>
Cc: gcc@gcc.gnu.org, Binutils <binutils@sourceware.org>
Subject: Re: [committed] exec-stack warning for test which wants executable stacks
Date: Mon, 25 Apr 2022 16:26:08 +0100 [thread overview]
Message-ID: <615c917b-1109-da5e-9727-a47f60f3e6bf@redhat.com> (raw)
In-Reply-To: <eec935c1-b81c-1383-c9d0-571273256363@gmail.com>
Hi Jeff,
Just FYI - I am also looking at adding in another warning. This time for
when the linker creates a PT_LOAD segment which has all of the RWX flags
set. At the moment my testing seems to show that it only causes problems
when a custom linker script is used that defines its own program headers
and does not provide separate headers for code and data.
Cheers
Nick
next prev parent reply other threads:[~2022-04-25 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 17:42 Jeff Law
2022-04-25 12:56 ` Martin Liška
2022-04-25 14:37 ` Jeff Law
2022-04-25 14:42 ` Nick Clifton
2022-04-25 14:59 ` Jeff Law
2022-04-25 15:26 ` Nick Clifton [this message]
2022-04-25 15:30 ` Jeff Law
2022-05-26 1:17 ` Hans-Peter Nilsson
2022-05-26 23:17 ` Hans-Peter Nilsson
2022-04-26 13:54 ` Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=615c917b-1109-da5e-9727-a47f60f3e6bf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=mliska@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).