From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
java-patches@gcc.gnu.org,
Ian Lance Taylor <iant@google.com>
Subject: Re: Remove obsolete Solaris 8 support
Date: Thu, 15 Mar 2012 14:41:00 -0000 [thread overview]
Message-ID: <yddipi6c4f1.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <201203122319.42906.ebotcazou@adacore.com> (Eric Botcazou's message of "Mon, 12 Mar 2012 23:19:42 +0100")
Eric Botcazou <ebotcazou@adacore.com> writes:
>> * Although libgcc/config/sparc/sol2-unwind.h could be simplified quite a
>> bit, perhaps we could go further: I wonder if the remaining nframes = 2
>> case really applies to Solaris 9. If not, one could massivly simplify
>> this code.
>
> Please no, let's keep being very conservative with this stuff.
If we are, we'll never learn if this code is needed on anything beyond
Solaris 8 and keep this cruft around basically forever. I'll at least
try a bootstrap with the nframes = 2 code ripped out with Solaris 9 FCS
libc and libthread (and of course the whole rest: latest Solaris 9, 10
and 11) and see if anything breaks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2012-03-15 14:41 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
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 [this message]
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=yddipi6c4f1.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=libstdc++@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).