From: Dennis Clarke <dclarke@blastwave.org>
To: gdb@sourceware.org
Subject: Re: Obsoleting Solaris 10 support
Date: Tue, 16 Oct 2018 18:41:00 -0000 [thread overview]
Message-ID: <35e07e9e-95ac-7341-9a84-5e8a77090226@blastwave.org> (raw)
In-Reply-To: <yddpnwakz2g.fsf@CeBiTec.Uni-Bielefeld.DE>
On 10/16/2018 05:42 AM, Rainer Orth wrote:
> Yesterday I've announced the obsoletion of Solaris 10 support in GCC 9
>
> https://gcc.gnu.org/ml/gcc/2018-10/msg00139.html
>
> I believe the same reasons cited there hold for GDB as well. Besides,
> we had some build failures recently that only occured on Solaris 10,
> creating work to support a rapidly dwindling or even vanished user base.
> Therefore, I wonder how best to handle this in GDB.
>
Looking at the gcc test results for the past few years it looks like
efforts have fallen off a cliff. Certainly I have lost a lot of
interest. I still have reasons to work with Apache and OpenSSL and a
few other places but even those reasons are going away.
2018
Results for 8.1.0 (genunix Fri May 11 08:23:40 GMT 2018) testsuite on
sparc64-sun-solaris2.10
Results for 8.1.0 (genunix intermediate2 Thu May 10 22:32:27 GMT 2018)
testsuite on sparc64-sun-solaris2.10
Results for 8.1.0 (genunix intermediate Wed May 9 03:28:19 GMT 2018)
testsuite on sparc64-sun-solaris2.10
Results for 8.1.0 (genunix Fri May 4 09:11:25 GMT 2018) testsuite on
sparc64-sun-solaris2.10
Results for 8.1.0 (GCC) testsuite on i386-pc-solaris2.11
Results for 8.1.0 (GCC) testsuite on i386-pc-solaris2.10
Results for 8.1.0 (GCC) testsuite on sparc-sun-solaris2.10
Results for 8.1.0 (GCC) testsuite on sparc-sun-solaris2.11
Results for 7.3.0 (genunix Mon Apr 16 19:59:50 GMT 2018) testsuite on
sparc64-sun-solaris2.10
2017
Results for 7.2.0 (genunix Thu Aug 24 11:51:52 GMT 2017) testsuite on
sparc64-sun-solaris2.10
Results for 7.2.0 (genunix Tue Aug 22 16:45:21 GMT 2017) testsuite on
sparc64-sun-solaris2.10
Results for 6.4.0 (genunix Tue Jul 25 02:19:47 GMT 2017) testsuite on
sparc64-sun-solaris2.10
Results for 6.4.0 (genunix Wed Jul 26 02:41:24 GMT 2017) testsuite on
sparc64-sun-solaris2.10
Results for 7.1.0 (GCC) testsuite on sparc-sun-solaris2.11
Results for 7.1.0 (GCC) testsuite on i386-pc-solaris2.12
Results for 7.1.0 (GCC) testsuite on sparc-sun-solaris2.12
2016
Results for 6.1.0 (tgcware64 6.1.0-1) testsuite on sparc64-sun-solaris2.10
Results for 6.1.0 (tgcware 6.1.0-1) testsuite on sparc-sun-solaris2.10
Results for 5.4.0 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.4.0 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.4.0 (GCC) testsuite on i386-pc-solaris2.11
Results for 5.4.0 (GCC) testsuite on sparc-sun-solaris2.12
Results for 5.4.0 (GCC) testsuite on sparc-sun-solaris2.12
Results for 5.4.0 (GCC) testsuite on i386-pc-solaris2.12
Results for 5.4.0 (GCC) testsuite on i386-pc-solaris2.12
Results for 5.4.0 (GCC) testsuite on i386-pc-solaris2.11
Results for 6.1.0 (GCC) testsuite on i386-pc-solaris2.10
Results for 6.1.0 (GCC) testsuite on sparc-sun-solaris2.11
Results for 6.1.0 (GCC) testsuite on sparc-sun-solaris2.12
Results for 6.1.0 (GCC) testsuite on i386-pc-solaris2.12
Results for 6.1.0 (GCC) testsuite on i386-pc-solaris2.11
2015
Results for 5.3.0 (tgcware 5.3.0-1) testsuite on sparc-sun-solaris2.10
Results for 5.3.0 (tgcware64 5.3.0-1) testsuite on sparc64-sun-solaris2.10
Results for 5.2.1 20151020 (GCC) testsuite on i386-pc-solaris2.11
Results for 5.2.0 (tgcware64 5.2.0-1) testsuite on sparc64-sun-solaris2.10
Results for 5.2.0 (tgcware 5.2.0-1) testsuite on sparc-sun-solaris2.10
Results for 4.9.3 (tgcware64 4.9.3-1) testsuite on sparc64-sun-solaris2.10
Results for 4.9.3 (tgcware 4.9.3-1) testsuite on sparc-sun-solaris2.10
Results for 4.9.3 (tgcware64 4.9.3-1) testsuite on sparc64-sun-solaris2.9
Results for 4.9.3 (tgcware 4.9.3-1) testsuite on sparc-sun-solaris2.9
Results for 4.8.5 (tgcware64 4.8.5-1) testsuite on sparc64-sun-solaris2.9
Results for 4.8.5 (tgcware 4.8.5-1) testsuite on sparc-sun-solaris2.9
Results for 4.9.3 (tgcware 4.9.3-1) testsuite on i386-pc-solaris2.9
Results for 4.8.5 (tgcware 4.8.5-1) testsuite on i386-pc-solaris2.9
Results for 4.9.3 (GCC) testsuite on i486-sun-solaris2.11
Results for 5.1.1 (GCC) testsuite on i386-pc-solaris2.12
Results for 5.1.1 (GCC) testsuite on i386-pc-solaris2.12
Results for 5.1.1 (GCC) testsuite on i386-pc-solaris2.12
Results for 5.1.1 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.1.1 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.1.1 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.1.1 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.1.0 (GCC) testsuite on sparc-sun-solaris2.11
Results for 5.1.0 (GCC) testsuite on i386-pc-solaris2.12
Results for 4.9.2 (genunix Fri Jan 2 11:56:03 GMT 2015) testsuite on
sparc64-sun-solaris2.10
There was considerable activity in the previous five years and I know
that I have been submitting results as far back as 1999 or so. However
the last five years clearly point the direction.
Dennis Clarke
next prev parent reply other threads:[~2018-10-16 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 9:42 Rainer Orth
2018-10-16 14:20 ` Joel Brobecker
2018-10-16 14:31 ` Rainer Orth
2018-10-16 16:39 ` Joel Brobecker
2018-10-16 18:21 ` Dennis Clarke
2018-10-17 12:39 ` Rainer Orth
2018-10-17 12:34 ` Rainer Orth
2018-10-16 18:41 ` Dennis Clarke [this message]
2018-10-17 12:42 ` Rainer Orth
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=35e07e9e-95ac-7341-9a84-5e8a77090226@blastwave.org \
--to=dclarke@blastwave.org \
--cc=gdb@sourceware.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