-
Bug
-
Resolution: Fixed
-
P3
-
10
-
b36
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8193752 | 11 | Roland Westrelin | P3 | Resolved | Fixed | team |
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
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
- backported by
-
JDK-8193752 -XX:+UseCountedLoopSafepoints alone doesn't disable strip mining with G1
-
- Resolved
-
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-