From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id B0A9F3858C54; Tue, 21 Mar 2023 00:03:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B0A9F3858C54
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1679357014;
	bh=3mJCBurJBHFJrW/lEJ6I4ZSqcOzdS43nKt/lfaIXUKw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=JUZ7mqYVuWY19d4R1I6uEcZp2L7qpokiz4n16X70/tWdP1VhYBnomNFee7M9pDdOt
	 Y1jfgQcxzDhJGVaG8irxHB6gCBWZ/OKjHvxD7g/q20AqtxCLZg7qQz2qX93FxJuKA3
	 fgFcf1UCf2ISyKV8g/6cv3K9XEx++AmBVyaNxrf4=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.1.2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-38274-4-4iaMayURB9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38274-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38274-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D38274

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.=