-
Bug
-
Resolution: Fixed
-
P4
-
9
-
None
-
b17
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8064088 | 8u45 | Attila Szegedi | P4 | Resolved | Fixed | b01 |
JDK-8055556 | 8u40 | Attila Szegedi | P4 | Resolved | Fixed | b04 |
JDK-8070325 | emb-8u47 | Attila Szegedi | P4 | Resolved | Fixed | team |
E.g.
var x = foo()
var a = 3;
a++; // becomes double instead of optimistic int
function foo() { return null };
The reason is that the first deoptimizing recompilation happens when "foo()" is invoked and the return value doesn't fit in an int. At this time, "a" is not yet initialized, so naively observing Undefined value turns its subsequent accessor into Object one. The fix is to avoid inferring expression types for undefined scoped variables (those for which Property.getCurrentType() == null), instead of presuming Object.
- backported by
-
JDK-8055556 Access to undefined scoped variables deoptimized too much
-
- Resolved
-
-
JDK-8064088 Access to undefined scoped variables deoptimized too much
-
- Resolved
-
-
JDK-8070325 Access to undefined scoped variables deoptimized too much
-
- Resolved
-
- relates to
-
JDK-8038396 8037534 breaks richards Octane benchmark
-
- Resolved
-