public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Freeze timing and questions
Date: Mon, 17 Dec 2001 10:01:00 -0000	[thread overview]
Message-ID: <10112171749.AA23338@vlsi1.ultra.nyu.edu> (raw)

    The point is to spend the next couple of months stabilizing the
    compiler.  That means that we find important bugs, from GNATS or
    elsewhere, and try to fix them.  It's OK if they're not regressions;
    now is a great time to fix that horrible bug that's been annoying you
    since 1996.  We are now, however, focusing on quality -- not new items
    for the 3.1 release announcement bullet list.

This is somewhat ambiguous as to what "important" means, but I'd
suggest a criteria that looks at the fix.  A local fix is acceptable
even for a minor bug, but fixes that are more complex or riskier for
some reason should only be done for more important bugs.

    This is OK, but at this point I think it is unreasonable to actually
    support Chill in 3.1; its status would be equivalent to the KDE
    patches in the contrib/ directory.

A trickier question is what about Ada?  Active work is under way to get
the current sources to work with 3.1, but so far the complete ACT test
suite has not passed on *any* target, though it's getting closer (probably
under a half dozen distinct problems on x86).  Since test suites for Ada have
not yet been set up in the GCC tree, there's a tradeoff between pulling over
all front-end changes from ACT, whether bugfixes or new features, which have
been heavily tested, or copying over just the bugfixes, resulting in a
source tree that hasn't been as tested.  My feeling is that the first is
best, at least for another few weeks or until the sources start passing
the complete test suite, but I'm not sure.

             reply	other threads:[~2001-12-17 17:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 10:01 Richard Kenner [this message]
2001-12-17 11:37 ` Mark Mitchell
2001-12-17 12:09   ` Geert Bosch
2001-12-17 12:20     ` Joseph S. Myers
2001-12-17 12:26       ` Mark Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2001-12-18  4:56 Richard Kenner
2001-12-18  8:06 ` Mark Mitchell
2001-12-17 12:53 Richard Kenner
2001-12-17 13:39 ` guerby
2001-12-17 14:11   ` Joseph S. Myers
2001-12-17 12:52 lucier
2001-12-17 12:48 Richard Kenner
2001-12-17 18:40 ` Mark Mitchell
2001-12-15 13:27 Joseph S. Myers
2001-12-15 13:45 ` David O'Brien
2001-12-17  9:37 ` Mark Mitchell
2001-12-17 12:17   ` Toon Moene
2001-12-17 12:20     ` Mark Mitchell
2001-12-18 14:48       ` Toon Moene
2001-12-17 13:28   ` Richard Henderson
2001-12-17 18:42     ` Mark Mitchell

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=10112171749.AA23338@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).