public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: Mainline in regression-fix mode after Thanksgiving
Date: Tue, 23 Nov 2004 01:16:00 -0000	[thread overview]
Message-ID: <200411230026.iAN0QqeO005220@sirius.codesourcery.com> (raw)


I've been staring at Bguzilla for about a week now trying to figure
out what to make of the fact that there are more than 200 regressions
open against GCC 3.4.  True, some of these are low-priority (MMIX or
Ada bugs for example) -- but most are not.  There are 110 wrong-code,
rejects-valid, or ice-on-valid regressions.  That's negative progress
from October 26th.

I realize that people are agressively using the compiler, and that
bugs reported is partially a function of the amount of use.  I also
understand that with all the changes we've got in this release, there
are bound to be some problems.  However, I think that we've got to
take steps to get things in hand.

Therefore, effective 12:01 AM Friday, November 26th PST, the usual
release-branch rules will be in effect on the mainline.  So,
regression-fixes only.  Patches submitted before that date can still
be applied, but other patches will need to be queued for either (a)
the mainline (if I lift the release-branch rules before we branch) or
(b) GCC 4.1 (if I do not).  Port/language maintainers please respect
this constraint.

The Objective-C++ situation is a special case; the SC has made it a
priority to get that functionality into 4.0.  Therefore, I'm going to
give Zem and Geoff until December 3rd to figure out what to do, and
convince anyone else who needs to be convinced.  Otherwise, I'm going
to postpone Objective-C++ until 4.1.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

             reply	other threads:[~2004-11-23  0:27 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  1:16 Mark Mitchell [this message]
2004-11-23  1:21 ` Kazu Hirata
2004-11-23  1:28   ` Diego Novillo
2004-11-23  1:31     ` Mark Mitchell
2004-11-23  1:37       ` Diego Novillo
2004-11-23 11:46       ` Nathan Sidwell
2004-11-23 16:09         ` Mark Mitchell
2004-11-23  2:15 ` Mike Stump
2004-11-23  2:31   ` Mark Mitchell
2004-11-23  3:00     ` Giovanni Bajo
2004-11-23  8:17       ` Daniel Berlin
2004-11-23  8:39     ` H. J. Lu
2004-11-23 17:19     ` Janis Johnson
2004-11-23 17:23       ` Giovanni Bajo
2004-11-23 18:02         ` Mark Mitchell
2004-11-23 18:20           ` Joe Buck
2004-11-23 18:34             ` Giovanni Bajo
2004-11-23 19:01               ` Joe Buck
2004-11-25 15:47                 ` Gerald Pfeifer
2004-11-23 18:03         ` Janis Johnson
2004-11-23 22:14         ` Mike Stump
     [not found]           ` <41A3B68A.5020408@cs.york.ac.uk>
2004-11-23 23:52             ` Mike Stump
2004-11-24 18:49             ` Giovanni Bajo
2004-11-24 19:39               ` Joe Buck
2004-11-24 18:44           ` Giovanni Bajo
2004-11-25 12:41             ` Richard Sandiford
2004-11-25 18:03               ` Mike Stump
2004-11-28 13:02       ` Toon Moene
2004-11-24 17:29 ` Joseph S. Myers
2004-11-24 17:32   ` Mark Mitchell
2004-11-24 17:38   ` Gabriel Dos Reis
2004-11-28 12:59 ` Toon Moene
2004-11-29  5:02   ` Mark Mitchell
2004-11-29 11:30     ` Richard Earnshaw
2004-11-29 13:53       ` Paul Brook
2004-11-29 14:06         ` Richard Earnshaw
2004-11-29 16:07           ` Andreas Schwab
2004-11-29 21:47             ` Phil Edwards
2004-11-29 21:59               ` Paul Brook
2004-11-29 23:27                 ` Phil Edwards
2004-11-30 22:49       ` Gerald Pfeifer
2004-11-23 20:05 Richard Kenner
2004-11-28 13:41 Richard Kenner

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=200411230026.iAN0QqeO005220@sirius.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    /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).