This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: c/7344: performance regression on huge case statements

From: Robert Schiele <rschiele at uni-mannheim dot de>
To: Nathanael Nerode <neroden at twcny dot rr dot com>
Cc: gcc-gnats at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org,nobody at gcc dot gnu dot org
Date: Fri, 18 Oct 2002 15:50:39 +0200
Subject: Re: c/7344: performance regression on huge case statements
References: <3DB00903.8020108@twcny.rr.com>

On Fri, Oct 18, 2002 at 09:13:39AM -0400, Nathanael Nerode wrote:
> So it's down to 28 seconds.  That's still technically a regression, but 
> it's no longer so horrible.  Is this enough to close the report, or 
> downgrade its priority from high?

On which system do you have 28 seconds?  How fast were older gcc
releases on this system?

From my point of view, this is acceptable, as most code fragments do
not consist of a switch statement with thousands of cases.  It is
again now compilable within a realistic time frame, so I think at
least the priority can be reduced.

I don't know the common policy, so I cannot tell whether the bug
should be closed, but I think if someone expects a realistic chance to
get this time lower, the bug should not yet been closed to prevent
forgetting it.

Robert

-- 
Robert Schiele			Tel.: +49-621-181-2517
Dipl.-Wirtsch.informatiker	mailto:rschiele@uni-mannheim.de

Attachment: msg00704/pgp00000.pgp
Description: PGP signature

References:
- Re: c/7344: performance regression on huge case statements
  - From: Nathanael Nerode

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]