-
Bug
-
Resolution: Fixed
-
P4
-
8
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8008059 | 8 | Roland Westrelin | P4 | Resolved | Fixed | b77 |
| JDK-8018016 | 7u45 | Roland Westrelin | P4 | Closed | Fixed | b01 |
| JDK-8008498 | 7u40 | Roland Westrelin | P4 | Closed | Fixed | b14 |
| JDK-8008094 | hs24 | Roland Westrelin | P4 | Resolved | Fixed | b33 |
Before incremental inlining inlines a new call site, it sanity checks the input state of the call node: if the call is in a part of the graph that is dead, there's no need to proceed with inlining and, the parser doesn't expect a strange input state anyway. One the check consists in testing the input edges to the call node that correspond to input arguments for top. Long/double arguments to a call are in 2 halves, one of which is top so incremental inlining will skip all calls with at least a long or double argument, mistaken them for dead calls.
This bug impacts the performance of the box2d test with nashorn (10-20% performance increase once fixed and LiveNodeCountInliningCutoff bumped to 30000).
This bug impacts the performance of the box2d test with nashorn (10-20% performance increase once fixed and LiveNodeCountInliningCutoff bumped to 30000).
- backported by
-
JDK-8008059 Incremental inlining mistakes some call sites for dead ones and doesn't inline them
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-8005071 Incremental inlining for JSR 292
-
- Resolved
-