JDK-8257027 : [JEP 390] Diagnose synchronization on @ValueBased classes
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-11-24
- Updated: 2020-12-14
- Resolved: 2020-12-08
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.
To download the current JDK release, click here.
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.
To download the current JDK release, click here.
| JDK 16 |
|---|
16 masterFixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8252182 :
|
|
|
JDK-8254273 :
|
Description
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 by JDK-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.]
Comments
|