-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b146
-
ppc
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8189881 | 8u172 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
JDK-8190609 | 8u171 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
JDK-8189239 | 8u162 | Goetz Lindenmaier | P4 | Resolved | Fixed | b03 |
JDK-8198062 | emb-8u171 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
On profiling some specific Neo4j workloads, some cases where a sequence of load (li) and compare (cmpld) can be
replaced by a single cmpldi instructions were identified. On replacing that sequence by a single instruction it's
possible to reduce the path length so the program is shorter, and therefore is faster.
Additionally, the 2 instruction sequence requires an additional register that with enough register pressure a
spill would be needed to accommodate that approach.
It's related to the discussion started here:
http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2016-October/024664.html
replaced by a single cmpldi instructions were identified. On replacing that sequence by a single instruction it's
possible to reduce the path length so the program is shorter, and therefore is faster.
Additionally, the 2 instruction sequence requires an additional register that with enough register pressure a
spill would be needed to accommodate that approach.
It's related to the discussion started here:
http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2016-October/024664.html
- backported by
-
JDK-8189239 PPC64: Use cmpldi instead of li/cmpld
- Resolved
-
JDK-8189881 PPC64: Use cmpldi instead of li/cmpld
- Resolved
-
JDK-8190609 PPC64: Use cmpldi instead of li/cmpld
- Resolved
-
JDK-8198062 PPC64: Use cmpldi instead of li/cmpld
- Resolved
1.
|
Enhancement backport request | Closed | Winston Yandi |