From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4332 invoked by alias); 5 May 2003 10:52:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 4307 invoked by uid 48); 5 May 2003 10:52:03 -0000 Date: Mon, 05 May 2003 10:52:00 -0000 Message-ID: <20030505105203.4306.qmail@sources.redhat.com> To: andreas@florath.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org From: giovannibajo@libero.it Reply-To: giovannibajo@libero.it, andreas@florath.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/10060: ICE on huge file (300k lines) X-SW-Source: 2003-05/txt/msg00271.txt.bz2 List-Id: Synopsis: ICE on huge file (300k lines) State-Changed-From-To: open->feedback State-Changed-By: bajo State-Changed-When: Mon May 5 10:52:02 2003 State-Changed-Why: Hello Andreas, I have troubles reproducing this because it either hits virtual memory exhausted or compiles correctly, depends on how many objects I make it generate. Would you please confirm that this is still a bug in GCC 3.3 or 3.4, and provide a minimal number of objects that must be generated to trigger it? It seems that compilation time grows O(n^2), so putting a big number means hours of compilation (assuming infinite memory). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10060