public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Joe Buck <jbuck@synopsys.COM>
Cc: geoffk@redhat.com, gcc@gcc.gnu.org
Subject: Re: Compiler for Red Hat Linux 8
Date: Tue, 17 Jul 2001 17:48:00 -0000	[thread overview]
Message-ID: <m2lmlnnjp1.fsf@kelso.bothner.com> (raw)
In-Reply-To: <200107172252.PAA24374@atrus.synopsys.com>

[Speaking for myself of course, not for my current employer, nor
my past Cygnus affliliation, nor in my status as rather depressed
RH stock-owner, nor SC member!]

Joe Buck <jbuck@synopsys.COM> writes:

> I do have concerns (that the world's largest concentration of gcc
> developers will be putting their energy into a fork of gcc, rather than
> the net gcc), but evidently you have decided for business reasons that
> this is the way to go.

I think this is an unfair way of characterizing it.  The work "fork" is
a loaded one, and not appropriate.  I don't see what you would expect
Red Hat to do.  They cannot commit to a non-existent 3.0.x or 3.1.x;
the latter will probably be too late anyway for RH 8, and they need to
start initial test builds RSN.  So they have to work off some release
or snapshot.  They would presumably also add bug-fixes, but they may
not add exactly the same set of bug fixes that correspond to any
particular 3.0.x, because they have a schedule and Gcc has a different
looser schedule.  This is SOP and the same thing everone else does,
not just for Gcc but also the kernel etc.

So I assumme your complaint isn't that RH 8's gcc will not correspond
exactly to any specific Gcc release (which is unavoidable unless they
refuse to apply bug-fixes that appears after the release they use),
but that they are considering using their internal development tree.
Well, they have to use *some* internal development tree, so what is
wrong in using the same one as GNUPro uses, assuming they work to
minimize differences from the FSF tree?

> glibc is a sensitive matter; a number of us got rather nervous to see a
> couple of glibc developers advocating the use of gcc-2.96-rh instead of
> getting the 3.0 problems fixed.

In this case I might be tempted to be more forceful ...
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/per/

  reply	other threads:[~2001-07-17 17:48 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 [this message]
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
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=m2lmlnnjp1.fsf@kelso.bothner.com \
    --to=per@bothner.com \
    --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).