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

>>>>> "H J Lu" writes:

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

	Various distributions and user communities frequently use patched
versions of GCC, but that does not mean that the variants need to be
incompatible or start from a non-FSF source base.  The two questions are:

1) What GCC sources should be used as the base for the patched version?
2) Should the patched version maintain binary compatibility with the base?

	I personally strongly encourage Red Hat to consider using the FSF
GCC release as the base.  This is not a question of either using the
vanilla FSF GCC release or using a completely separate branch.  There are
other options besides those two extreme positions.

	I also personally encourage Red Hat to maintain compatibility with
the FSF GCC releases.

	Red Hat employs a large number of highly skilled GCC developers.
If GCC 3.0 or the GCC trunk is not stable enough / correct enough to use
in a GNU/Linux distribution, Red Hat's developers can work to improve and
stabilize a particular FSF GCC source base as effectively as any other GCC
source base.

	Red Hat's GNUPro "devo" source base is synchronized with the FSF
sources and, therefore, contains roughly as many problems as the FSF
sources.  A Red Hat 8 branch in GNUPro would need a similar amount of
stabilization work and performance improvement as the FSF sources.

	Maybe Red Hat could request a branch in the FSF GCC repository to
which they could have exclusive write access for their own development
effort -- using their own patches and acceptance criteria?  Maybe the
generic "GNU/Linux GCC" branch for all distributors, which another person
proposed, is the solution.

	I would like to find a way for Red Hat to develop their Red Hat
Linux 8 GCC release from the FSF GCC sources.  I think that we can find a
solution more easily by starting with a discussion of Red Hat's
requirements and how to fit those into the FSF GCC development environment
instead of starting from the pre-defined, limited proposals which have
been mentioned so far.

Thanks, David

	P.S. Speaking for myself; representing neither IBM nor the GCC
Steering Committee.

===============================================================================
David Edelsohn                                      T.J. Watson Research Center
dje@watson.ibm.com                                  P.O. Box 218
+1 914 945 4364 (TL 862)                            Yorktown Heights, NY 10598

  reply	other threads:[~2001-07-18 14:28 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
2001-07-18 14:28             ` David Edelsohn [this message]
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=200107182128.RAA29256@makai.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@redhat.com \
    --cc=hjl@lucon.org \
    --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).