-
Enhancement
-
Resolution: Fixed
-
P4
-
21, 25, 26
-
b05
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8364809 | 25.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | master |
In CTW profiling, I noticed we spend a lot of time doing inline cache verification when nmethods are unloaded. Due to the nature of CTW, we unload _a lot_ of nmethods. Since the goal for CTW is to stress the compilers themselves, not inline caches in particular (I assume those are blank even, given almost no real code is executed), it makes sense to disable that verification for CTW.
- backported by
-
JDK-8364809 CTW: Disable inline cache verification
-
- Resolved
-
- relates to
-
JDK-8361180 Disable CompiledDirectCall verification with -VerifyInlineCaches
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk25u/2a68b5d0
-
Commit(master) openjdk/jdk/aa191119
-
Review(master) openjdk/jdk25u/59
-
Review(master) openjdk/jdk/26016
(1 links to)