From: Mike Stump <mrs@windriver.com>
To: Franz.Sirl-kernel@lauterbach.com, gcc@gcc.gnu.org
Subject: Re: RedHat 7.0 + gcc-2.96, what's going on with gcc releases?
Date: Tue, 01 Aug 2000 13:57:00 -0000 [thread overview]
Message-ID: <200008012057.NAA09251@kankakee.wrs.com> (raw)
> Date: Tue, 01 Aug 2000 18:39:54 +0200
> From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
> the just released rh70 beta contains a gcc-2.96 snapshot as the main
> compiler it seems.
Ok.
> 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?
No.
> 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.
So? I don't see a problem as those bugs reports are more relevant
than bug reports against 2.95.2, if our quality was up high enough in
their release. They do have the resources to test and assure quality,
and I expect they use them, so I don't see a problem.
I consider it unfortunate, but that is the risk we take of not serving
our users. RedHat happens to be a user.
I am in the same situation. I needed a certain feature in the
compiler, it was only in a newer compiler, and I developed and shipped
a 2.96 era compiler to my customers. Life goes on. And next week (or
next month), I'll do it again, for all the same reasons all over
again.
This is SOP. I don't see it going away real soon.
Anyway, my point is, just because a company needs to do this from time
to time, doesn't mean we should contort what we are doing or take
immediate action because of it. We should fold it in and if we think
we can make changes that lessen the need for other companies to do
this, at a cost that we find reasonable, then we should do it.
The maybe more interesting point, would be the shared library
numbering scheme, C++ binary compatibility issues and so on.
next reply other threads:[~2000-08-01 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 13:57 Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-01 9:40 Franz Sirl
2000-08-01 10:21 ` Nick Ing-Simmons
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=200008012057.NAA09251@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@gcc.gnu.org \
/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).