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 middle-end/38274] why the option "-fstack-protector-all" doesn't works?
Date: Tue, 21 Mar 2023 00:03:33 +0000 [thread overview]
Message-ID: <bug-38274-4-4iaMayURB9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38274-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38274
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
-fstack-protector (-all) does not detect all buffer overflows and is not
designed that way (or even documented that way). It only adds one space at the
end of the stack to detect if there was a buffer overflow but it is also
aligned so it might be further out than just one location too.
next parent reply other threads:[~2023-03-21 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-38274-4@http.gcc.gnu.org/bugzilla/>
2023-03-21 0:03 ` pinskia at gcc dot gnu.org [this message]
2023-03-21 0:05 ` pinskia at gcc dot gnu.org
2008-11-26 9:26 [Bug c/38274] New: " zuogang at huawei dot com
2008-11-29 3:11 ` [Bug middle-end/38274] " pinskia at gcc dot gnu dot org
2008-12-01 10:14 ` zuogang at huawei dot com
2008-12-24 1:48 ` pinskia at gcc dot gnu dot org
2008-12-24 2:55 ` howarth at nitro dot med dot uc dot edu
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-38274-4-4iaMayURB9@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).