JDK-8235981 : Introduce a flag to enable JVM intrinsics
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 15
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- Submitted: 2019-12-16
- Updated: 2021-03-22
- Resolved: 2020-04-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 15 |
|---|
15Resolved  |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Introduce a way to enable JVM intrinsics from command-line. Right now, there's no way to introduce experimental intrinsics which are turned off by default and let users enable them on their side. There's -XX:DisableIntrinsic= present to *disable* intrinsics. Instead of introducing -XX:EnableIntrinsic= equivalent, it would be nice to have a new option which supersede both and supports both enabling and disabling arbitrary set of intrinsics. As an example: -XX:ControlIntrinsic=+_dabs,-_fabs,-_getClass It makes sense to require -XX:+UnlockExperimentalVMOptions when enabling intrinsics.
Comments
|