This is the mail archive of the gcc@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: We're out of tree codes; now what?


On 3/19/07, Doug Gregor <doug.gregor@gmail.com> wrote:
On 19 Mar 2007 19:12:35 -0500, Gabriel Dos Reis <gdr@cs.tamu.edu> wrote:
> similar justifications for yet another small% of slowdown have been
> given routinely for over 5 years now.  small% build up; and when they
> build up, they don't not to be convincing ;-)

But what is the solution? We can complain about performance all we
want (and we all love to do this), but without a plan to fix it we're
just wasting effort. Shall we reject every patch that causes a slow
down? Hold up releases if they are slower than their predecessors?
Stop work on extensions, optimizations, and bug fixes until we get our
compile-time performance back to some predetermined level?

This usually happens at least for some people. Actually compile time performance is a bug no matter which way we look at it so you are going to introduce one bug for another, no thanks.

-- Pinski


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