This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/31827] limits-exprparen.c: Pid 2297 received a SIGSEGV for stack growth failure
- From: "davek at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 1 Feb 2011 04:03:24 +0000
- Subject: [Bug middle-end/31827] limits-exprparen.c: Pid 2297 received a SIGSEGV for stack growth failure
- Auto-submitted: auto-generated
- References: <bug-31827-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31827
--- Comment #12 from Dave Korn <davek at gcc dot gnu.org> 2011-02-01 04:03:02 UTC ---
(In reply to comment #11)
> Recreated this on linux x86_64 with gcc 4.6-20110129. Running ulimit -a shows
> me that the default stack limit is 8192 and increasing this to 18000 allows the
> test to complete at all optimization levels that are tested by make check.
> Running at 17000 fails.
This has gotten worse over the past couple of months; I fixed it on cygwin a
while ago by turning up the stack size, finding that it needed somewhere
between 10MB and 12MB on that target; now it's just started failing again.
I don't know at what point we should consider this a compile-time performance
regression. Paolo, even a 30% reduction seems like a good idea to me; why not
submit that patch you developed?