JDK-8181292 : Backport Rename internal Unsafe.compare methods from 10 to 9
- Type: Bug
- Component: core-libs
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2017-05-30
- Updated: 2017-06-19
- Resolved: 2017-06-06
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 10 | JDK 9 |
|---|---|
10Fixed  |
9 b174Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The fix for JDK-8159995 to rename internal Unsafe compareAndSwap methods to compareAndSet (and associated intrinsic names in HotSpot) will make it harder for 166 and Graal to support both Java 9 and 10. The patches for JDK-8159995 and JDK-8180479 should be backported. Given the current processes in place to forward port 9 fixes to 10 and with duplicate bug ID restrictions in place the most expedient approach is to create an explicit backport issue for 9.
Comments
|