-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 17, 18
-
Component/s: hotspot
-
b24
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8289056 | 17.0.5-oracle | Tobias Hartmann | P4 | Resolved | Fixed | b01 |
| JDK-8289746 | 17.0.5 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
Adapted description from: https://github.com/openjdk/jdk/pull/5903#issuecomment-957443870
Our CI currently only runs -XX:-TieredCompilation in combination with CompileThreshold which is not whitelisted. This means that IR matching is not performed in that case. That's the reason why we have not detectedJDK-8275086 in our testing. I think the IR framework should be improved to just ignore any CompileThreshold flag settings and allow IR matching to be performed with -XX:-TieredCompilation in our CI.
Our CI currently only runs -XX:-TieredCompilation in combination with CompileThreshold which is not whitelisted. This means that IR matching is not performed in that case. That's the reason why we have not detected
- backported by
-
JDK-8289056 [IR Framework] Whitelist and ignore CompileThreshold
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/a5e273d8
-
Commit
openjdk/jdk/7a140af2
-
Review
openjdk/jdk17u-dev/523
-
Review
openjdk/jdk/6312
(1 links to)