From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Matz via Binutils <binutils@sourceware.org>
Subject: Re: RFC: Should we have all targets default to only creating an executable stack when explicitly requested ?
Date: Thu, 21 Apr 2022 18:00:51 +0200 [thread overview]
Message-ID: <87o80uifyk.fsf@igel.home> (raw)
In-Reply-To: <alpine.LSU.2.20.2204211428380.32194@wotan.suse.de> (Michael Matz via Binutils's message of "Thu, 21 Apr 2022 15:00:26 +0000 (UTC)")
On Apr 21 2022, Michael Matz via Binutils wrote:
> On this I disagree, as per above. If I'm using standard features of my
> language of choice I'm going to be non-plussed if that required linker
> options.
That would only be needed if the compiler produces object files without
an explicit stack note on platforms where executable stacks are the
default.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-04-21 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 11:28 Nick Clifton
2022-04-21 11:44 ` Jan Beulich
2022-04-21 14:44 ` Nick Clifton
2022-04-21 15:31 ` Jan Beulich
2022-04-21 11:52 ` Andreas Schwab
2022-04-21 15:00 ` Michael Matz
2022-04-21 16:00 ` Andreas Schwab [this message]
2022-04-22 11:11 ` Nick Clifton
2022-04-25 13:25 ` Michael Matz
2022-04-22 11:41 ` Martin Liška
2022-04-25 13:46 ` Sam James
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=87o80uifyk.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
/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).