From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18636 invoked by alias); 26 Apr 2002 00:45:31 -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 18599 invoked by uid 61); 26 Apr 2002 00:45:28 -0000 Date: Thu, 25 Apr 2002 17:45:00 -0000 Message-ID: <20020426004528.18598.qmail@sources.redhat.com> To: anton@mips.complang.tuwien.ac.at, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org From: rth@gcc.gnu.org Reply-To: rth@gcc.gnu.org, anton@mips.complang.tuwien.ac.at, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c/2160: signal 11 when compiling large generated program X-SW-Source: 2002-04/txt/msg01383.txt.bz2 List-Id: Synopsis: signal 11 when compiling large generated program State-Changed-From-To: analyzed->closed State-Changed-By: rth State-Changed-When: Thu Apr 25 17:45:27 2002 State-Changed-Why: This is the known computed-goto cfg manipulation problem. We've got nearly complete connectivity between a very large number of blocks, and we eat all that ram and time futzing with the edges between them. As such, I'm closing this as a duplicate of 4313, which identifies the problem more clearly. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2160