This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/69639] [6/7/8 Regression] FAIL: gcc.c-torture/compile/limits-exprparen.c
- From: "nightstrike at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 06 Aug 2017 03:16:24 +0000
- Subject: [Bug target/69639] [6/7/8 Regression] FAIL: gcc.c-torture/compile/limits-exprparen.c
- Auto-submitted: auto-generated
- References: <bug-69639-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69639
nightstrike <nightstrike at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nightstrike at gmail dot com
--- Comment #9 from nightstrike <nightstrike at gmail dot com> ---
This affects 8-trunk on x86_64 cygwin, as well. The default size of the stack
for cc1 is:
$ peflags -x /tmp/b2/gcc/cc1.exe
/tmp/b2/gcc/cc1.exe: stack reserve size : 12582912 (0xc00000) bytes
Setting it to 0xd00000 and 0xe00000 also fail. Setting it to 0xf00000 works.
I didn't go further than that to see where between 14 and 15 megs it starts
working.
Can we just boost the default stack size of cc1.exe by a couple megs for
affected hosts?