From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc@gcc.gnu.org
Subject: Obsolete Solaris 11.3 support
Date: Tue, 13 Dec 2022 13:26:08 +0100 [thread overview]
Message-ID: <yddmt7rebhb.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
Solaris 11.3 has reached the end of its support live, as can be seen in
the following overview based on
https://www.oracle.com/us/support/library/lifetime-support-hardware-301321.pdf,
p.40:
Release GA Date Last Premier Extended GCC
Update Support Support Obsoletion Removal
Solaris 8 Feb 2000 Feb 2002 Mar 2009 Mar 2012 Mar 2011 Mar 2012
Solaris 9 Mar 2002 Sep 2005 Oct 2011 Oct 2014 May 2013 Apr 2014
Solaris 10 Jan 2005 Jan 2013 Jan 2018 Jan 2021 May? 2019 May? 2020
Solaris 11.3 Oct 2015 Aug 2018 Jan 2021 Jan 2024 Dec? 2022 May? 2023
There are some features missing in Solaris 11.3 (dl_iterate_phdr, pipe2)
that make continued support more difficult, especially when it gets to
getting workarounds into upstream codebases like LLVM or Golang that
don't support anything but Solaris 11.4.
Therefore I think it's time to obsolete support for anything before
Solaris 11.4 in GCC 13, thus removing it in GCC 14.
There's one highly unfortunate side effect, though: the only public
Solaris 11.3 build system (gcc211 in the GCC Compile Farm) cannot be
upgraded to Solaris 11.4. I'm currently trying to get one or more
alternative systems in place to avoid that issue.
I'm going to post patches for the actual obsoletion and an entry for
wwwdocs shortly.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
reply other threads:[~2022-12-13 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=yddmt7rebhb.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc@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).