public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Joe Buck <jbuck@synopsys.COM>
Cc: Andreas Jaeger <aj@suse.de>, Geoff Keating <geoffk@redhat.com>,
	gcc@gcc.gnu.org
Subject: Re: Compiler for Red Hat Linux 8
Date: Wed, 18 Jul 2001 13:31:00 -0000	[thread overview]
Message-ID: <20010718133057.B16537@lucon.org> (raw)
In-Reply-To: <200107182021.NAA07274@atrus.synopsys.com>

On Wed, Jul 18, 2001 at 01:21:59PM -0700, Joe Buck wrote:
> HJ writes:
> > What may
> > happpen is noone can use the to-be-released gcc 3.0.1 to build the
> > whole Linux distribution before it is released. They may take a gcc
> > snapshot and go from there. When they finally find all the compiler
> > bugs, gcc 3.0.1 has been released. Then they will start all over
> > again. As the result, you still need to make gcc 3.0.2 if you want to
> > use it to build the whole Linux distribution.
> 
> If so, then we'll make 3.0.2, and because of scheduling, some people may
> release GNU/Linux distros with 3.0.1+patches because 3.0.2 wasn't out
> yet.

The same thing can happen with 3.0.2 ... That means the current
unmodified *released* gcc may not be usable for Linux. That will
last at least from one bug fix release to the next one. If it happens
more than half a year within a year, people may say you shouldn't use
the unmodified *released* gcc on Linux.


H.J.

  reply	other threads:[~2001-07-18 13:31 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 13:04 Geoff Keating
2001-07-17 15:52 ` Joe Buck
2001-07-17 17:48   ` Per Bothner
2001-07-18  8:55     ` Joseph S. Myers
2001-07-17 18:24 ` Craig Rodrigues
2001-07-18  2:41 ` Andreas Jaeger
2001-07-18  9:03   ` H . J . Lu
2001-07-18 12:01     ` Joe Buck
2001-07-18 12:46       ` H . J . Lu
2001-07-18 13:22         ` Joe Buck
2001-07-18 13:31           ` H . J . Lu [this message]
2001-07-18 14:28             ` David Edelsohn
2001-07-18 15:03               ` Joern Rennecke
2001-07-18 15:12                 ` David Edelsohn
2001-07-18 15:24                   ` Joe Buck
2001-07-18 17:05                     ` H . J . Lu
2001-07-19  4:56                     ` Toon Moene
2001-07-18 15:41                 ` Joseph S. Myers
2001-07-18 16:23                   ` H . J . Lu
2001-07-18 12:18     ` Sergey Ostrovsky
2001-07-18 15:19       ` Ken Whaley
2001-07-18 15:30         ` Toon Moene
2001-07-18 15:59           ` Ken Whaley
2001-07-18 16:08             ` Toon Moene
2001-07-18 13:30   ` Gerald Pfeifer
2001-07-19  5:17     ` Andreas Jaeger
2001-07-19 12:23       ` Gerald Pfeifer
2001-07-18 19:07   ` LinuxVN
2001-07-18 13:44 ` Toon Moene
2001-07-17 17:37 mike stump
2001-07-17 20:00 Benjamin Kosnik
2001-07-18 13:21 Benjamin Kosnik
2001-07-18 14:33 Geoff Keating
2001-07-18 14:41 dewar
2001-07-18 15:29 ` Geoff Keating
2001-07-18 17:50   ` Joe Buck
2001-07-18 18:59 ` Michael Eager
2001-07-18 19:26   ` Justin Guyett
2001-07-19  9:05     ` Mark Mitchell
2001-07-19 19:28   ` akbar A.
2001-07-18 22:10 ` Per Bothner
2001-07-18 22:19   ` Joe Buck
2001-07-18 22:38     ` Per Bothner
2001-07-18 23:00       ` Alex Rosenberg
2001-07-19 14:05       ` Jonathan Larmour
2001-07-18 20:02 dewar
2001-07-19  0:29 Bernard Dautrevaux
2001-07-19  1:16 ` Toon Moene
2001-07-19  1:36 Bernard Dautrevaux
2001-07-19  2:40 ` Joseph S. Myers
2001-07-19  3:02 ` Roman Zippel
2001-07-19  3:12 ` Russ Allbery
2001-07-19  4:33 dewar
2001-07-19 10:49 dewar
2001-07-19 23:16 Bernard Dautrevaux

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=20010718133057.B16537@lucon.org \
    --to=hjl@lucon.org \
    --cc=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@redhat.com \
    --cc=jbuck@synopsys.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).