From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12040 invoked by alias); 15 Jan 2003 16:27:40 -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 12020 invoked by uid 61); 15 Jan 2003 16:27:40 -0000 Date: Wed, 15 Jan 2003 16:27:00 -0000 Message-ID: <20030115162740.12019.qmail@sources.redhat.com> To: eggert@twinsun.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: bangerth@dealii.org Reply-To: bangerth@dealii.org, eggert@twinsun.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/6798: [3.2/3.3/3.4 regression] very long compile time with large case-statement X-SW-Source: 2003-01/txt/msg00962.txt.bz2 List-Id: Old Synopsis: cc1 -O2 in semi-infinite loop on sparc New Synopsis: [3.2/3.3/3.4 regression] very long compile time with large case-statement State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Wed Jan 15 08:27:38 2003 State-Changed-Why: I can also reproduce this on a Linux machine. The testcase is basically an enormous yacc-generated switch-statement, with about 2000 cases and a lot of cross-jumping. I killed the compilation after about 10 minutes. The code compiled in just 24 seconds with 2.95 even with -O2, so this is a regression. I attach a significantly cleaned up testcase as "testcase.i". W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6798