Currently ClassLoaderData::Claim values are simple enums, which is prone to value coercion issues like shown in JDK-8297349.
Some quick investigation showed the following problems when doing that:
* the code uses the enum value as bitfield, or'ing values together. This could be fixed by operator overloading
* this adds a circular dependency due to additional includes needed (in memory/iterator.hpp); an option is to factor out the claim values into a separate header.
Some quick investigation showed the following problems when doing that:
* the code uses the enum value as bitfield, or'ing values together. This could be fixed by operator overloading
* this adds a circular dependency due to additional includes needed (in memory/iterator.hpp); an option is to factor out the claim values into a separate header.
- relates to
-
JDK-8297349 Parallel: Use correct claim value for CLD oop iteration in PSScavengeCLDClosure
-
- Resolved
-