public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Giovanni Bajo" <giovannibajo@libero.it>
Cc: <espie@nerim.net>, <gcc@gcc.gnu.org>
Subject: Re: A quick summary of gcc compilation speed from a political point of view
Date: Tue, 20 Jan 2004 16:54:00 -0000	[thread overview]
Message-ID: <m3ptde5zxt.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <310301c3df60$d26896b0$34b82997@bagio>

"Giovanni Bajo" <giovannibajo@libero.it> writes:

| Gabriel Dos Reis wrote:
| 
| > Yeah, but more and more people now seem to be swearing only by
| > bugzilla
| 
| It's a fact that our releases and regression fixes are driven by the
| bugreports we get.

Bug reports are key factors, but they are not the only one.  And
basing GCC releases _only_ on things one sees in bugzilla would be
inappropriate. 

The compile-time regression is not a new topic. It was noticed before
we released GCC-3.3, but then we made a clear commitment that it will
be a release criteria for GCC-3.4.  Now, some people seem to narrow
their views only on bugzilla.  Bugzilla is a great tool, but
somethings are just not that easy to fill in there.

-- Gaby

  reply	other threads:[~2004-01-20 16:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 10:04 Marc Espie
2004-01-20 12:05 ` Giovanni Bajo
2004-01-20 13:38   ` Gabriel Dos Reis
2004-01-20 13:51     ` Giovanni Bajo
2004-01-20 14:07       ` Gabriel Dos Reis
2004-01-20 14:22         ` Giovanni Bajo
2004-01-20 16:54           ` Gabriel Dos Reis [this message]
2004-01-20 13:59     ` Marc Espie
2004-01-20 22:01   ` Marc Espie
2004-01-21 11:15     ` Zack Weinberg
2004-01-20 13:55 ` Jan Hubicka
2004-01-20 13:59   ` Jan Hubicka
2004-01-20 16:54   ` Diego Novillo
2004-01-20 16:07 Benjamin Kosnik
2004-01-20 20:09 Nathanael Nerode

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ptde5zxt.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=espie@nerim.net \
    --cc=gcc@gcc.gnu.org \
    --cc=giovannibajo@libero.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).