Hi Kim,
Can we amend the JEP itself to be not solely about hotspot.
Since it affects other areas I think that
1) They may need to be compiled with C++14 enabled whether they use new
features or not
2) They may want - or need - to adopt C++11 or C++14 features too.
You already know that soon we will upgrade the harfbuzz 3rd party
library used by 2D
and it will bring along the need to use C++11 features and I had no plan
to propose a JEP for that.
So I don't want to be asked why we didn't do one when hotspot did !
So this really ought to be a JDK JEP whilst of course explaining that
hotspot is expected
to be the primary adopter.
BTW the JEP (https://bugs.openjdk.java.net/browse/JDK-8208089) still says
> For Solaris: Add the |-std=c++14| compiler option. .....
So I am sure there is still some room to update the JEP :-)
-phil.
On 6/5/20, 12:52 AM, Kim Barrett wrote:
[Changes are only to the build system, but since the changes have jdk-wide
effect I’ve cc’d what I think are the relevant dev lists.]
This change is part of JEP 347; the intent is to target JDK 16.
Please review this change to the building of C++ code in the JDK to
enable the use of C++14 language features. This change does not make
any code changes to use new features provided by C++11 or C++14.
This requires trimming the supported compiler versions, moving the
minimum supported versions forward (significantly, in some cases).
The new minimums are based on compiler documentation rather than
testing. It may be that more recent versions are actually required.
This change needs to be tested on platforms not supported by Oracle.
The JEP test plan includes additional Oracle testing beyond what I’ve done.
CR:
https://bugs.openjdk.java.net/browse/JDK-8246032
Webrev:
https://cr.openjdk.java.net/~kbarrett/8246032/open.02/
Testing:
mach5 tier1-5 on Oracle supported platforms.
Performance testing showed no significant changes in either direction.
Build-only (no tests) for linux-arm32, linux-s390x, linux-ppc64le
