From: Eric Botcazou <botcazou@adacore.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Probe emission in fstack-clash-protection
Date: Wed, 03 May 2023 10:22:34 +0200 [thread overview]
Message-ID: <4479420.LvFx2qVVIh@arcturus> (raw)
In-Reply-To: <f2d80347-91d2-d06d-1859-ac6d7c64b8cd@gmail.com>
> That may ultimately be better for -fstack-check to make it more robust,
> but it still wouldn't be a viable alternative for stack clash protection
> for the reasons laid out in that blog post.
Well, -fstack-check does that when it's possible, e.g. on Windows, but it's
not on x86[_64]/Linux where you *cannot* probe below the stack pointer.
--
Eric Botcazou
next prev parent reply other threads:[~2023-05-03 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 4:36 Varun Kumar E
2023-05-03 5:46 ` Jeff Law
2023-05-03 8:22 ` Eric Botcazou [this message]
2023-05-03 11:56 ` Florian Weimer
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=4479420.LvFx2qVVIh@arcturus \
--to=botcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
/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).