From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
java-patches@gcc.gnu.org, Eric Botcazou <ebotcazou@adacore.com>,
Ian Lance Taylor <iant@google.com>
Subject: Re: Remove obsolete Solaris 8 support
Date: Mon, 12 Mar 2012 18:58:00 -0000 [thread overview]
Message-ID: <CABu31nPpznfxLD9AnrRtaOZt2RGEQtzSafXtrjM8Z9202Xhrzg@mail.gmail.com> (raw)
In-Reply-To: <43D69F8C-3FCE-4915-A211-6F04466DB8CB@comcast.net>
On Mon, Mar 12, 2012 at 7:37 PM, Mike Stump <mikestump@comcast.net> wrote:
> On Mar 12, 2012, at 10:44 AM, Rainer Orth wrote:
>> Since even extended support for Solaris 8 ends by March 31st, this patch
>> removes Solaris 8 support from mainline.
>
> One of the nice things about gcc is that gcc usually still works, long after a vendor has abandoned a machine. I rather like that gcc will just work, unlike vendor software, which often says, please buy a new machine. One doesn't have to remove support in gcc for something, just because a vendor doesn't support it. That said, truly crufty things, should go.
Personally, I'd be in favor of removing any target for which no test
results have been posted for the last, say, 2 GCC release series.
Otherwise there isn't any measure for the quality for such a target.
There've been GCC release series where a complete port failed to
build...
Ciao!
Steven
next prev parent reply other threads:[~2012-03-12 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 17:45 Rainer Orth
2012-03-12 18:31 ` Ian Lance Taylor
2012-03-12 18:38 ` Mike Stump
2012-03-12 18:49 ` Richard Kenner
2012-03-12 18:56 ` Rainer Orth
2012-03-12 18:49 ` Rainer Orth
2012-03-12 18:59 ` Mike Stump
2012-03-12 18:58 ` Steven Bosscher [this message]
2012-03-12 20:14 ` Jonathan Wakely
2012-03-12 20:43 ` Tom Tromey
2012-03-12 20:43 ` Tom Tromey
2012-03-12 22:19 ` Eric Botcazou
2012-03-15 14:41 ` Rainer Orth
2012-03-15 14:53 ` Eric Botcazou
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=CABu31nPpznfxLD9AnrRtaOZt2RGEQtzSafXtrjM8Z9202Xhrzg@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=java-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=ro@cebitec.uni-bielefeld.de \
/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).