This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/82358] [8 regression] i386/stack-check-11.c fail
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 02 Oct 2017 18:05:38 +0000
- Subject: [Bug target/82358] [8 regression] i386/stack-check-11.c fail
- Auto-submitted: auto-generated
- References: <bug-82358-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82358
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
?!?
First, I don't get this failure. Andrey, what is your precise target
configuration?
Martin -- the code you show is exactly what is should be.
In the "before" case we have a stack allocation of 13768 bytes, then probes
into that allocation. That is not safe WRT stack-clash as you could get an
async signal between the allocation and probing points and the async handler
would be running with a clashed stack/heap.
The "after" case we see 4 distinct allocations and probes, which is exactly
what we want.