JDK-8192908 : -XX:+UseCountedLoopSafepoints alone doesn't disable strip mining with G1
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 10
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-12-01
- Updated: 2019-09-13
- Resolved: 2017-12-07
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 11 |
|---|---|
10 b36Fixed  |
11Fixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
There's a small inconsistency in the way UseCountedLoopSafepoints/LoopStripMiningIter is treated for G1: default is +UseCountedLoopSafepoints, LoopStripMiningIter=1000 but with: java -XX:+UseCountedLoopSafepoint a message is printed: When counted loop safepoints are enabled, LoopStripMiningIter must be at least 1 (a safepoint every 1 iteration): setting it to 1 but LoopStripMiningIter is set to 1000 So if you want the pre loop strip mining behaviour of +UseCountedLoopSafepoint, you need to pass -XX:+UseCountedLoopSafepoint -XX:LoopStripMiningIter=1
Comments
|