public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Stabilization of the egcs tree
Date: Tue, 22 Dec 1998 22:52:00 -0000	[thread overview]
Message-ID: <9662.914395915@hurl.cygnus.com> (raw)

A few more notes.

What I would like to see first is all the major platforms bootstrapping
with normal bootstrapping options.

ie, I don't want to worry about -O9, -mblahblah -ffoobar at this point.  I
want to get our basic "make bootstrap" working across all the major platforms.

Once that has settled down we should proceed in an _organized_ manner to test
the various -O options, then machine independent options, then finally
machine dependent options.

I do not expect to get through all this in 2 weeks, but I do want to see
significant progress on stabilizing the tree over the next 2 weeks.  We need
to start fixing more bugs than we are introducing.

*I* will be ignoring bootstrapping problems with nonstandard options until
we get "make bootstrap" solid.  There's no use in reporting problems with
nonstandard bootstraps until we get the standard bootstrap working well again.

I will also ignore non-bugfix patches submitted after midnight Dec 22 EST
until we have made significant progress stabilizing the tree.

We've got serious problems with the tree that need to be sorted out ASAP;
the quicker we sort them out, the quicker we can get back to the fun parts
of this project (and the quicker we can seriously think about egcs-1.2
timetables).

jeff

ps.  This is also going to delay the merge from gcc2 until after the tree
has stabilized.  Contrary to an uninformed post, the merge from gcc2 has
not been checked in and thus we do not have i18n support or any of the other
gcc2 changes.


             reply	other threads:[~1998-12-22 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-22 22:52 Jeffrey A Law [this message]
1998-12-27  1:07 ` Michael Hayes
1998-12-27  8:55   ` Jeffrey A Law

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=9662.914395915@hurl.cygnus.com \
    --to=law@hurl.cygnus.com \
    --cc=egcs@cygnus.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).