Enhance the work done in JDK-8242263 to warn about synchronization performed on any class that is declared with a @ValueBased annotation.
The same behaviors as implemented byJDK-8242263 should apply—VM abort, logged warning, or JFR event.
The -XX:DiagnoseSyncOnPrimitiveWrappers flag should probably be renamed to indicate that it's a check on all value-based classes. (It is probably *not* useful to have two different knobs, one for primitives and one for other value-based classes.)
---
[This is a development task related to JEP 390. Commits to the valhalla/jep390 branch should be handled with subtasks, and this issue will be closed when the JEP is integrated.]
The same behaviors as implemented by
The -XX:DiagnoseSyncOnPrimitiveWrappers flag should probably be renamed to indicate that it's a check on all value-based classes. (It is probably *not* useful to have two different knobs, one for primitives and one for other value-based classes.)
---
[This is a development task related to JEP 390. Commits to the valhalla/jep390 branch should be handled with subtasks, and this issue will be closed when the JEP is integrated.]
- blocks
-
JDK-8249100 JEP 390: Warnings for Value-Based Classes
- Closed
- relates to
-
JDK-8257845 Integrate JEP 390
- Resolved
-
JDK-8273486 Zero: Handle DiagnoseSyncOnValueBasedClasses VM option
- Resolved
-
JDK-8252181 [JEP 390] Define & apply annotation jdk.internal.ValueBased
- Resolved
-
JDK-8242263 Diagnose synchronization on primitive wrappers
- Resolved
(2 links to)