public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Ing-Simmons <nik@tiuk.ti.com>
To: gcc@gcc.gnu.org, Franz.Sirl-kernel@lauterbach.com
Cc: "Randy J. Ray" <rjray@tzimisce.soma.redhat.com>
Subject: Re: RedHat 7.0 + gcc-2.96, what's going on with gcc releases?
Date: Tue, 01 Aug 2000 10:21:00 -0000	[thread overview]
Message-ID: <200008011717.SAA10586@mikado.tiuk.ti.com> (raw)
In-Reply-To: <4.3.2.7.2.20000801175835.03596100@mail.lauterbach.com>

Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:
>Hi,
>
>the just released rh70 beta contains a gcc-2.96 snapshot as the main 
>compiler it seems. 

Why do they bundle such bleading edge stuff?!
(The had a broken perl snapshot in 5.2 ...)

Randy had promised me they had learnt their lesson...

>Since gcc-2.96/gcc-3.0 is nowhere near a release AFAIK, 
>I would like to know if it makes sense to drop the planned (?) gcc-2.95.3 
>in favor of a gcc-2.96 release with the libstdc++-v3 and new-abi stuff 
>still disabled? AFA I can tell, this should be possible with a relatively 
>short stabilization phase...
>
>I for myself think this makes sense, cause as soon as rh70 is out, there 
>will probably more bug reports against the snapshot that RH uses than for 
>gcc-2.95.x simply due the large userbase of RH.
>
>Franz.
-- 
Nick Ing-Simmons <nik@tiuk.ti.com>
Via, but not speaking for: Texas Instruments Ltd.

  reply	other threads:[~2000-08-01 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-01  9:40 Franz Sirl
2000-08-01 10:21 ` Nick Ing-Simmons [this message]
2000-08-01 13:57 Mike Stump

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=200008011717.SAA10586@mikado.tiuk.ti.com \
    --to=nik@tiuk.ti.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rjray@tzimisce.soma.redhat.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).