Horton

Re: Solaris compiler status

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>, Peter Eisentraut <peter@eisentraut.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-09-03T21:56:22Z
Lists: pgsql-hackers 
On Thu, Sep 4, 2025 at 2:42 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:
> > On 3 Sep 2025, at 07:47, Peter Eisentraut <peter@eisentraut.org> wrote:
> >> So, can we declare that we don't support this compiler anymore?
> >> (gcc is readily available and seems to work alright, so I'm not saying the OS is no longer viable.)
>
> > +1 based on the findings above.
>
> +1, given the lack of complaints it certainly appears that
> nobody cares.

+1.

Last release 2017, and development had ended by 2020 according to a
well known Sun/Oracle engineer:

https://forums.oracle.com/ords/apexds/post/is-developer-studio-abandoned-and-discontinued-by-oracle-3285

Commits

  1. Remove traces of support for Sun Studio compiler

  2. Remove checks for no longer supported GCC versions

  3. Remove stray semicolon at global scope

  4. Provide vectored variants of smgrread() and smgrwrite().

  5. Convert *GetDatum() and DatumGet*() macros to inline functions