New candidate JEP: 362: Deprecate the Solaris and SPARC Ports (original) (raw)

Baesken, Matthias matthias.baesken at sap.com
Thu Nov 7 08:28:52 UTC 2019

Hello Mikael, the xlc 16.1 / xlclang++ docu talks about C++11/14 :

https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS218-567

„Introduction of two new compiler invocation paths to provide compilation functionality that support the C11, C++11 and C++14 standards.”

But not about C++17 .

So we are there more or less on the same level as Oracle Studio 12.6 , where C++11/14 is supported too , but not 17 .

Best regards, Matthias

On Nov 6, 2019, at 5:00 AM, Baesken, Matthias <matthias.baesken at sap.com<mailto:matthias.baesken at sap.com>> wrote:

We’re looking at adopting a newer version of the C++ standard (C++14 or C++17) along with the features that come with it. Oracle Studio does not support the full C++14 standard, and AFAIK does not support C++17 at all.

Hello,

The Oracle® Developer Studio 12.6: C++ User's Guide from 2017 says :

https://docs.oracle.com/cd/E77782_01/pdf/E77789.pdf

"Oracle Developer Studio12.6 provides full support for C++11"

"Oracle Developer Studio12.6 provides full support for the C++14 Standard"

(chapters 1.1.1 and 1.1.2 ).

So C++14 features should not be an issue on Solaris . What C++17 features do you plan to use (this might be also interesting for our AIX port, so it needs to be handled carefully) ? I think we have to be very careful with using new features of the C++ standard , with or without deprecating / removing Solaris and SPARC Ports .

To be discussed - there’s a draft JEP here: https://bugs.openjdk.java.net/browse/JDK-8208089

More information about the jdk-dev mailing list