-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 21, 25
-
b10
We have been looking at some related compiler behaviors, and realized that in the absence of profiling data, C2 routinely uncommon-traps a lot of code that is presumed to be never executed. This apparently is a norm in CTW tests: CTW runners never execute code, and so only the most basic java.base classes are having any profile. This seems to limit the scope of CTW testing.
I think we need to run CTW in the mode that exposes more code to the compiler optimizations.
Case in point:JDK-8348572, which reliably fails with more aggressive compilation mode.
I think we need to run CTW in the mode that exposes more code to the compiler optimizations.
Case in point:
- causes
-
JDK-8349915 CTW: Lots of level 3 compiles are done at level 2 after JDK-8348570
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
- relates to
-
-
- Open
-
- links to
-
Commit(master)
openjdk/jdk/10791477
-
Review(master)
openjdk/jdk/23296