From: Bruce Korb <bkorb@gnu.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
libstdc++@gcc.gnu.org, java-patches@gcc.gnu.org,
Uros Bizjak <ubizjak@gmail.com>,
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: Sat, 19 Apr 2014 17:58:00 -0000 [thread overview]
Message-ID: <5352BB86.3030407@gnu.org> (raw)
In-Reply-To: <ydd7g6p8qy7.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
On 04/16/14 04:16, Rainer Orth wrote:
> I've already verified that trunk fails to build no sparc-sun-solaris2.9
> and i386-pc-solaris2.9. Bootstraps on {i386,sparc}-*-solaris2.{10,11}
> (and x86_64-unknown-linux-gnu for good measure) are in progress. I'll
> verify that there are no unexpected fixincludes changes and differences
> in gcc configure results.
> fixincludes:
> * inclhack.def (math_exception): Bypass on *-*-solaris2.1[0-9]*.
> (solaris_int_types): Remove.
> (solaris_longjmp_noreturn): Remove.
> (solaris_mutex_init_2): Remove.
> (solaris_once_init_2): Remove.
> (solaris_sys_va_list): Remove.
> * fixincl.x: Regenerate.
> * tests/base/iso/setjmp_iso.h: Remove.
> * tests/base/pthread.h [SOLARIS_MUTEX_INIT_2_CHECK]: Remove.
> [SOLARIS_ONCE_INIT_2_CHECK]: Remove.
> * tests/base/sys/int_types.h: Remove.
> * tests/base/sys/va_list.h: Remove.
Removing dinkleberry fixes by the platform maintainer always has my approval. :)
prev parent reply other threads:[~2014-04-19 17:58 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
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 [this message]
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=5352BB86.3030407@gnu.org \
--to=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 \
--cc=ubizjak@gmail.com \
/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).