JDK-8260579 : PPC64 and S390 builds failures after JDK-8260467
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 17
  • Priority: P1
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-01-28
  • Updated: 2021-07-15
  • Resolved: 2021-01-28
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 17
17 b08Fixed
Related Reports
Relates :  
Description
For example:

Creating support/modules_libs/java.base/server/libjvm.so from 889 file(s)
/home/shade/trunks/jdk/src/hotspot/cpu/s390/methodHandles_s390.cpp: In static member function 'static void MethodHandles::verify_klass(MacroAssembler*, Register, VMClassID, Register, Register, const char*)':
/home/shade/trunks/jdk/src/hotspot/cpu/s390/methodHandles_s390.cpp:83:32: error: 'VMClassses' has not been declared
   83 |   InstanceKlass** klass_addr = VMClassses::klass_addr_at(klass_id);
      |                                ^~~~~~~~~~
/home/shade/trunks/jdk/src/hotspot/cpu/s390/methodHandles_s390.cpp:84:18: error: 'VMClassses' has not been declared
   84 |   Klass* klass = VMClassses::klass_at(klass_id);
      |                  ^~~~~~~~~~

This is an obvious typo in "VMClassses".
Comments
[~shade] thanks for fixing this. I did test ppc64 and s390, but the affected code was in ASSERT only and I used a product build :-(. I'll adjust my test scripts to avoid making the same mistake again.
28-01-2021

Changeset: a68c6c2a Author: Aleksey Shipilev <shade@openjdk.org> Date: 2021-01-28 12:00:59 +0000 URL: https://git.openjdk.java.net/jdk/commit/a68c6c2a
28-01-2021