public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/103863] We need a warning for loss of no-exec stacks
Date: Thu, 30 Dec 2021 02:04:57 +0000 [thread overview]
Message-ID: <bug-103863-4-AQoeUSpzNt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103863-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103863
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Component|c |driver
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think the warning needs to be implemented in the linker rather than in GCC
because the linker is what decides if there are executable stacks are needed or
not.
next prev parent reply other threads:[~2021-12-30 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 1:59 [Bug c/103863] New: " noloader at gmail dot com
2021-12-30 2:04 ` pinskia at gcc dot gnu.org [this message]
2021-12-30 2:05 ` [Bug driver/103863] " pinskia at gcc dot gnu.org
2021-12-30 2:27 ` noloader at gmail dot com
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=bug-103863-4-AQoeUSpzNt@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).