P4
The original discussion started at:
https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2019-April/007245.html
According to the latest document of Arm DDI0487, which is ARM Architecture Reference Manual ARMv8, for ARMv8-A architecture profile at https://developer.arm.com/docs/ddi0487/latest, the new CPU implementer code CPU_AMPERE (0xC0) is going to be added into the "enum Family" defined in hotspot/cpu/aarch64/vm_version_aarch64.hpp.
The reason why ISO8859-1 (ASCII) representation is not used for this entry specially is: 0xC0 belongs to the list of "The extended ASCII codes" (https://www.ascii-code.com/) which would not display correctly in multiple terminals and caused build warnings "multichar". -Wno-multichar option in makefiles can suppress warnings but will not be used here since real typos in code could be missed if disabling the check.
https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2019-April/007245.html
According to the latest document of Arm DDI0487, which is ARM Architecture Reference Manual ARMv8, for ARMv8-A architecture profile at https://developer.arm.com/docs/ddi0487/latest, the new CPU implementer code CPU_AMPERE (0xC0) is going to be added into the "enum Family" defined in hotspot/cpu/aarch64/vm_version_aarch64.hpp.
The reason why ISO8859-1 (ASCII) representation is not used for this entry specially is: 0xC0 belongs to the list of "The extended ASCII codes" (https://www.ascii-code.com/) which would not display correctly in multiple terminals and caused build warnings "multichar". -Wno-multichar option in makefiles can suppress warnings but will not be used here since real typos in code could be missed if disabling the check.