-
Bug
-
Resolution: Fixed
-
P3
-
11, 17, 19, 20
-
b04
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8291308 | 19.0.2 | Richard Reingruber | P3 | Resolved | Fixed | b01 |
JDK-8291142 | 19.0.1 | Richard Reingruber | P3 | Resolved | Fixed | b04 |
JDK-8289039 | 19 | Richard Reingruber | P3 | Resolved | Fixed | b29 |
JDK-8291011 | 17.0.5-oracle | Tobias Hartmann | P3 | Resolved | Fixed | b04 |
JDK-8291015 | 17.0.5 | Richard Reingruber | P3 | Resolved | Fixed | b01 |
JDK-8291007 | 11.0.17-oracle | Tobias Hartmann | P3 | Resolved | Fixed | b04 |
JDK-8291848 | 11.0.17 | Goetz Lindenmaier | P3 | Resolved | Fixed | b02 |
assert(_oprs_len[mode] < maxNumberOfOperands) failed: array overflow
fails when C1 compiles a method with 8 integer and 13 float parameters because LIR_OpVisitState::maxNumberOfOperands is 20 which is too small because on ppc 8 integer + 13 float = 21 parameters can be passed in registers (see SharedRuntime::java_calling_convention()).
- backported by
-
JDK-8289039 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
-
JDK-8291007 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
-
JDK-8291011 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
-
JDK-8291015 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
-
JDK-8291142 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
-
JDK-8291308 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
-
JDK-8291848 C1: LIR_OpVisitState::maxNumberOfOperands too small
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/ce8367f4
-
Commit openjdk/jdk17u-dev/612cca38
-
Commit openjdk/jdk19/3f5e48a4
-
Review openjdk/jdk11u-dev/1299
-
Review openjdk/jdk17u-dev/567
-
Review openjdk/jdk19/51