public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Richard Biener <richard.guenther@gmail.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>,
	 "<debian-sparc@lists.debian.org>"
	<debian-sparc@lists.debian.org>
Subject: Re: [COMMITTED] Remove obsolete Solaris 11.3 support
Date: Fri, 10 May 2024 13:48:24 +0200	[thread overview]
Message-ID: <ydda5kxubuf.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <ffff4cc66f86f619965afffb55e92a9e3fe6b4a0.camel@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Fri, 10 May 2024 12:31:39 +0200")

Hi John,

> On Fri, 2024-05-10 at 12:14 +0200, Richard Biener wrote:
>> > Because I wasn't subscribed to gcc-patches and I'm also only subscribed now
>> > without receiving messages due to the large message volume on this list.
>> 
>> https://gcc.gnu.org/gcc-13/changes.html
>> 
>> > The problem with announcements on developer mailing lists is usually
>> > that they
>> > usually don't reach any users. I was made aware of this change only when I
>> > checked about the recent changes to GCC Git.
>> 
>> Where do you expect such announcement then?
>
> That's a difficult question, to be honest. From a user perspective, it's hard to
> track these upstream announcements. I would argue that most users don't follow
> all such changes in the upstream projects they are using and, to be honest,
> I really
> wouldn't have expected that Solaris 11.3 would be considered obsolete.

users don't have to follow such announcements at all unless they build
GCC from source.  And those that do better should.  As I mentioned, if
they try, they'll get the info from configure anyway.

> If it had been for Solaris 7, 8 or 9, I would totally understand. But even
> Solaris 10
> is something that Oracle still supports [1].

Right, and you pay an arm and a leg for that.  Yet, Solaris 10 support
was removed from GCC 10 back in 2019 without much fuss.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2024-05-10 11:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09  6:31 John Paul Adrian Glaubitz
2024-05-10  3:14 ` jake@pawlicker.com jake@pawlicker.com
2024-05-10 11:07   ` Peter Tribble
2024-05-11 18:54     ` John Paul Adrian Glaubitz
2024-05-10  8:20 ` Rainer Orth
2024-05-10  8:53   ` John Paul Adrian Glaubitz
2024-05-10 10:14     ` Richard Biener
2024-05-10 10:31       ` John Paul Adrian Glaubitz
2024-05-10 11:48         ` Rainer Orth [this message]
2024-05-10 11:44       ` Rainer Orth
2024-05-10 13:43         ` Stuff Received
2024-05-10 13:59           ` Rainer Orth
2024-05-10 19:27             ` Jan Engelhardt
2024-05-10 19:37               ` Rainer Orth
2024-05-10 11:57     ` Rainer Orth
  -- strict thread matches above, loose matches on Subject: below --
2024-05-02 14:06 Rainer Orth
2024-05-02 21:45 ` Ian Lance Taylor

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=ydda5kxubuf.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=debian-sparc@lists.debian.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=richard.guenther@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).