JDK-8193244 : [Graal] abort if trying to use CMS with Graal
Type:Enhancement
Component:hotspot
Sub-Component:compiler
Affected Version:10,11
Priority:P4
Status:Resolved
Resolution:Fixed
Submitted:2017-12-08
Updated:2018-06-26
Resolved:2018-04-02
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Since CMS is scheduled for removal[1], we should actively not support it instead of spending resources on fixing Graal to work with it.
[1] http://openjdk.java.net/jeps/291
Comments
Excellent, thanks for adding a whitelist in Graal. Yes, we will enable CMS again in our build of HotSpot.
26-06-2018
Note, Hotspot JDK-8184349 changes in JDK 11 will prevent using Graal with CMS. We also switched off testing of such combination.
26-06-2018
As of https://github.com/oracle/graal/commit/3ff06d1617240c5e6b7747d1305a060fd5c69369, CMS support in Graal is restored. However, if using with JDK 11, you'll need a customized build that undoes http://hg.openjdk.java.net/jdk/jdk/rev/e5d741569070#l5.1 .
26-06-2018
Can Graal continue to allow CMS, with the proviso that testing and fixing issues with CMS will not be a priority? That would allow open jdk to support CMS with Graal via possible community contributions rather than summarily closing off that possibility?
26-06-2018
Will be resolved in OpenJDK by JDK-8199755.
02-04-2018
This is already fixed upstream (https://github.com/oracle/graal/commit/bec1dc92e18e1058f0e5c4a0bccd5afef38637c6) and will be pulled into OpenJDK in the next Graal sync.