From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: mikestump@comcast.net, ebotcazou@adacore.com,
gcc-patches@gcc.gnu.org, iant@google.com,
java-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Remove obsolete Solaris 8 support
Date: Mon, 12 Mar 2012 18:56:00 -0000 [thread overview]
Message-ID: <ydd7gypir7o.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20120312184916.EAE8F33C83@vlsi1.gnat.com> (Richard Kenner's message of "Mon, 12 Mar 2012 14:49:16 EDT")
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
>> 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.
>
> I agree. If it's not causing a serious maintenance issue, I see no
> reason to remove it.
It does, unfortunately: Solaris 8 is even worse wrt. to C99 and POSIX.1
conformance than Solaris 9, especially in the areas of TLS and thread
support, as I've found the hard way during the GCC 4.7 cycle. There are
all sorts of quirks, and the OS is now 12 years old. I see better ways
to spend my (volunteer) time.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2012-03-12 18:56 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 [this message]
2012-03-12 18:49 ` Rainer Orth
2012-03-12 18:59 ` Mike Stump
2012-03-12 18:58 ` Steven Bosscher
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=ydd7gypir7o.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=java-patches@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=libstdc++@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).