-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
b04
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8045222 | 8u25 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8035384 | 8u20 | Aleksey Shipilev | P4 | Resolved | Fixed | b03 |
JDK-8053226 | emb-8u26 | Aleksey Shipilev | P4 | Resolved | Fixed | b17 |
In seems we have it unconditionally turned on. It makes the inlining
policy a little less understandable to have additional branch here and
there. Should we purge this option from the VM codebase?
policy a little less understandable to have additional branch here and
there. Should we purge this option from the VM codebase?
- backported by
-
JDK-8035384 Remove -XX:+-UseOldInlining
- Resolved
-
JDK-8045222 Remove -XX:+-UseOldInlining
- Resolved
-
JDK-8053226 Remove -XX:+-UseOldInlining
- Resolved
- relates to
-
JDK-8035585 Restore UseOldInlining in jdk8u
- Resolved
-
JDK-8232355 Two obsolete flags have the wrong obsolete version in 8u
- Resolved
-
JDK-8241122 Remove unimplemented InlineTree constructor definition from parse.hpp
- Resolved
(1 relates to)