JDK-8150552 : Remove -XX:+AggressiveOpts
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9,10,11,12
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-02-24
- Updated: 2019-02-12
- Resolved: 2018-10-24
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 12 |
|---|
12 b17Fixed  |
Related Reports
|
Blocks :
|
Sub Tasks
|
JDK-8212915 :
|
Description
-XX:+AggressiveOpts has been used as a catch-all method of enabling various experimental performance features, mostly targetted to improve score on very specific benchmarks. Most things it affected has been removed or integrated over time, e.g., JDK-8024826, leaving the behavior of the flag ill-defined and prone to cause more issues than it'll solve. I suggest removing the flag altogether, possibly in a staggered fashion similar to MaxPermSize where it will produce a warning message in JDK X and then refuse to run in JDK X+1.
Comments
|