-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b44
-
ppc
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8082024 | emb-9 | Severin Gehwolf | P4 | Resolved | Fixed | b44 |
JDK-8086264 | 8u65 | Severin Gehwolf | P4 | Resolved | Fixed | b01 |
JDK-8074300 | 8u60 | Severin Gehwolf | P4 | Resolved | Fixed | b06 |
JDK-8137342 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8076766 | emb-8u60 | Severin Gehwolf | P4 | Resolved | Fixed | team |
ZERO_ARCHDEF is used to enable architecture specific code. Currently, this gets defined as ZERO_ARCHDEF=PPC which is wrong since the hotspot build expects either PPC32 or PPC64 and silently undefines PPC if neither is defined.
This may lead to wrongly generated code.
This may lead to wrongly generated code.
- backported by
-
JDK-8074300 ZERO_ARCHDEF incorrectly defined for PPC/PPC64 architectures
-
- Resolved
-
-
JDK-8076766 ZERO_ARCHDEF incorrectly defined for PPC/PPC64 architectures
-
- Resolved
-
-
JDK-8082024 ZERO_ARCHDEF incorrectly defined for PPC/PPC64 architectures
-
- Resolved
-
-
JDK-8086264 ZERO_ARCHDEF incorrectly defined for PPC/PPC64 architectures
-
- Resolved
-
-
JDK-8137342 ZERO_ARCHDEF incorrectly defined for PPC/PPC64 architectures
-
- Resolved
-