JEP 291: Deprecate the Concurrent Mark Sweep (CMS) Garbage Collector
jesper.wilhelmsson at oracle.com
Fri Jul 1 15:02:37 UTC 2016
Den 1/7/16 kl. 16:39, skrev Andrew Haley:
> On 01/07/16 15:36, Jon Masamitsu wrote:
>> Do you have a suggestion on how continued support for CMS in OpenJDK
>> would work? I've been told that if CMS is built in the binaries that Oracle
>> distributes, then customers will expect Oracle to support it. Regardless
>> of what the release notes say.
> How are they to know that it's in there? All you have to do is
> disable the option in Oracle builds.
One important reason to get rid of CMS is to get a cleaner and more maintainable
code base. Disabling the option will not get us there.
The code in the cms directory can pretty much be ignored in the build, but there
is a lot of shared code that could be substantially cleaned up if CMS is no
longer supported. This cleanup needs to be done and the parts that CMS still
needs must be moved to the cms directory in order for us to be able to say that
this code is no longer supported.
More information about the hotspot-gc-dev