From: Uros Bizjak <ubizjak@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
java-patches@gcc.gnu.org, Bruce Korb <bkorb@gnu.org>,
Eric Botcazou <ebotcazou@adacore.com>,
Ian Lance Taylor <iant@google.com>,
David Edelsohn <dje.gcc@gmail.com>,
Paolo Bonzini <bonzini@gnu.org>
Subject: Re: Remove obsolete Solaris 9 support
Date: Wed, 16 Apr 2014 17:28:00 -0000 [thread overview]
Message-ID: <CAFULd4Zj-J0F9Qif9rtDAcDP4Oz8RB=gcX7=kLUC=8v0Zb98yQ@mail.gmail.com> (raw)
In-Reply-To: <ydd7g6p8qy7.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
On Wed, Apr 16, 2014 at 1:16 PM, Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
> Now that 4.9 has branched, it's time to actually remove the obsolete
> Solaris 9 configuration. Most of this is just legwork and falls under
> my Solaris maintainership.
>
> A couple of questions, though:
>
> * Uros: I'm removing all sse_os_support() checks from the testsuite.
> Solaris 9 was the only consumer, so it seems best to do away with it.
This is OK, but please leave sse-os-check.h (and corresponding
sse_os_support calls) in the testsuite. Just remove the Solaris 9
specific code from sse-os-check.h and always return 1, perhaps with
the comment that all currently supported OSes support SSE
instructions.
Uros.
next prev parent reply other threads:[~2014-04-16 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 11:17 Rainer Orth
2014-04-16 16:00 ` Eric Botcazou
2014-04-16 17:28 ` Uros Bizjak [this message]
2014-04-22 12:36 ` Rainer Orth
2014-04-23 12:51 ` Uros Bizjak
2014-04-16 19:59 ` Ian Lance Taylor
2014-04-19 8:04 ` Andrew Haley
2014-04-22 12:42 ` Rainer Orth
2014-04-22 13:22 ` Mark Wielaard
2014-04-22 15:18 ` Andrew Hughes
2014-04-23 9:04 ` Rainer Orth
2014-04-19 17:58 ` Bruce Korb
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='CAFULd4Zj-J0F9Qif9rtDAcDP4Oz8RB=gcX7=kLUC=8v0Zb98yQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=bkorb@gnu.org \
--cc=bonzini@gnu.org \
--cc=dje.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=java-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--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).