-
Enhancement
-
Resolution: Fixed
-
P4
-
21
-
b15
At subtype checks, we use profile data if both:
1- and the test hasn't failed before
2- if it reports a unique class
If neither 1- nor 2- is true, then we ignore profile data. It seems unfortunate as if 1- is false, there's still a good chance the class reported by profile data is the common case and testing for it before going to the full blown subtype check would be faster overall. Even if 2- is false, but only 2 classes are ever seen at the subtype check, it's likely that emitting 1 comparison with each before the full blown subtype check is faster overall.
1- and the test hasn't failed before
2- if it reports a unique class
If neither 1- nor 2- is true, then we ignore profile data. It seems unfortunate as if 1- is false, there's still a good chance the class reported by profile data is the common case and testing for it before going to the full blown subtype check would be faster overall. Even if 2- is false, but only 2 classes are ever seen at the subtype check, it's likely that emitting 1 comparison with each before the full blown subtype check is faster overall.
- relates to
-
JDK-8320296 [lworld] Fix profiling at array store subtype checks in Valhalla
-
- Resolved
-
-
-
- Resolved
-
-
-
- Open
-
-
-
- Resolved
-
-
-
- Resolved
-
(2 links to)