-
Enhancement
-
Resolution: Fixed
-
P4
-
9, 10
-
b21
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8260784 | openjdk8u292 | Andrew Hughes | P4 | Resolved | Fixed | b01 |
JDK-8208908 | 8u201 | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8205196 | 8u192 | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8216728 | emb-8u201 | Kevin Walls | P4 | Resolved | Fixed | master |
JDK-8213370 | 7u221 | Kevin Walls | P4 | Resolved | Fixed | b01 |
- The Node class defines "uint Node::ideal_reg()" and "uint Node::NotAMachineReg" is a special value which "must be > max. machine register".
- The Type class has "int ideal_reg()" which deals in the same values.
This mostly results in some implicit potentially narrowing conversions in various places, due to the chosen value of NotAMachineReg. However, the initialization of the Type::_type_info array includes some having their ideal_reg member initialized to NotAMachineReg. Such implicit narrowings are forbidden by C++11.
The invalid narrowings could be worked around via casts. But that's building in assumptions about the value of NotAMachineReg. And it seems like it might be better to remove the inconsistency, if possible.
[This is a followup to
- backported by
-
JDK-8205196 Inconsistent types for ideal_reg
- Resolved
-
JDK-8208908 Inconsistent types for ideal_reg
- Resolved
-
JDK-8213370 Inconsistent types for ideal_reg
- Resolved
-
JDK-8216728 Inconsistent types for ideal_reg
- Resolved
-
JDK-8260784 Inconsistent types for ideal_reg
- Resolved
- relates to
-
JDK-8145549 Add support for Visual Studio 2015 Community edition
- Closed
-
JDK-8160353 narrowing conversion error is occurred with GCC 6
- Resolved
-
JDK-8257192 Integrate AArch64 JIT port into 8u
- Resolved