This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/27794] stack explosion
- From: "sje at cup dot hp dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jun 2006 17:47:17 -0000
- Subject: [Bug bootstrap/27794] stack explosion
- References: <bug-27794-226@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from sje at cup dot hp dot com 2006-06-05 17:47 -------
I shrank my stack to match yours and still can't reproduce this problem.
What were the configure options on this? Did it use --enable-checking=all
or something like that? Also, the log makes it look like it died when running
xgcc -dumpspecs. This seems hightly unlikely since dumping the spec should be
a very simple, very fast thing for the compiler to do. Whas this a parallel
build where the error message might be coming from a different command? Is the
-dumpspec the first thing the bootstrap does with the new compiler? I.e. does
any run of xgcc cause a stack growth failure?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27794