From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10329 invoked by alias); 5 Jun 2006 17:47:36 -0000 Received: (qmail 10258 invoked by uid 48); 5 Jun 2006 17:47:17 -0000 Date: Mon, 05 Jun 2006 18:22:00 -0000 Message-ID: <20060605174717.10257.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug bootstrap/27794] stack explosion In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "sje at cup dot hp dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-06/txt/msg00579.txt.bz2 List-Id: ------- 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