-
Enhancement
-
Resolution: Fixed
-
P3
-
8u60
-
b08
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8074492 | 9 | Attila Szegedi | P3 | Resolved | Fixed | b54 |
JDK-8085604 | emb-9 | Attila Szegedi | P3 | Resolved | Fixed | team |
JDK-8087041 | 8u65 | Attila Szegedi | P3 | Resolved | Fixed | b01 |
JDK-8138462 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b01 |
JDK-8076955 | emb-8u60 | Attila Szegedi | P3 | Resolved | Fixed | team |
RuntimeCallSites come into play for Runtime nodes where at least on of the arguments is a primitive and one is an Object, previously used to leverage what little static type information that we had.
We can probably remove all this logic now, in the optimistic world, but we should benchmark without it to make sure that it has no impact. We don't believe it does.
This would hopefully be a drastic simplification of code complexity for very little performance gain. The performance gain would be completely gained by the optimistic architecture anyway,
We can probably remove all this logic now, in the optimistic world, but we should benchmark without it to make sure that it has no impact. We don't believe it does.
This would hopefully be a drastic simplification of code complexity for very little performance gain. The performance gain would be completely gained by the optimistic architecture anyway,
- backported by
-
JDK-8074492 Investigate if RuntimeCallSite linkage can be removed
-
- Resolved
-
-
JDK-8076955 Investigate if RuntimeCallSite linkage can be removed
-
- Resolved
-
-
JDK-8085604 Investigate if RuntimeCallSite linkage can be removed
-
- Resolved
-
-
JDK-8087041 Investigate if RuntimeCallSite linkage can be removed
-
- Resolved
-
-
JDK-8138462 Investigate if RuntimeCallSite linkage can be removed
-
- Resolved
-
- duplicates
-
JDK-8010699 Eventually retire RuntimeNodes
-
- Closed
-
(1 duplicates)