This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/6798: [3.2/3.3/3.4 regression] very long compile timewith large case-statement
- From: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: s dot bosscher at student dot tudelft dot nl, gcc-gnats at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org,eggert at twinsun dot com
- Cc: bangerth at ticam dot utexas dot edu
- Date: Wed, 12 Mar 2003 13:07:05 +0100 (CET)
- Subject: Re: optimization/6798: [3.2/3.3/3.4 regression] very long compile timewith large case-statement
- Reply-to: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
On 11 Mar, Steven Bosscher wrote:
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6798
>
> Volker, you said you saw this on Linux? I don't see this bug on
> i586-linux,
> so I hope you can confirm this so we can close this PR, or else we
> should try
> to find out if this is a target-specific problem.
>
> Greetz
> Steven
Sorry, but that was Wolfgang and not me (I just put the code into an
attachment):
| State-Changed-From-To: feedback->open
| State-Changed-By: reichelt
| State-Changed-When: Wed Jan 15 02:18:06 2003
| State-Changed-Why:
| Attachment received.
| 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.
Regards,
Volker