JDK-8234893 : ARM32: build failure after JDK-8234387
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 14
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • CPU: aarch32
  • Submitted: 2019-11-27
  • Updated: 2019-12-10
  • Resolved: 2019-11-29
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 14
14 b26Fixed
Related Reports
Duplicate :  
Relates :  
Description
Ideal node missing: R8RegP
assert fails /ws/workspace/jdk-dev/label/linux-arm/type/b11/src/hotspot/share/adlc/archDesc.cpp 484: Failed lookup of ideal node

Comments
URL: https://hg.openjdk.java.net/jdk/jdk/rev/70021dbed82b User: bulasevich Date: 2019-11-29 08:29:19 +0000
29-11-2019

operand iRegP() %{ constraint(ALLOC_IN_RC(ptr_reg)); match(RegP); match(R0RegP); match(R1RegP); match(R2RegP); match(RExceptionRegP); match(R8RegP); match(R9RegP); match(RthreadRegP); // FIXME: move to sp_ptr_RegP? match(R12RegP); match(LRRegP); match(sp_ptr_RegP); match(store_ptr_RegP); format %{ %} interface(REG_INTER); %} R8RegP and R9RegP declarations are missing while, for example, R0RegP is there: operand R0RegP() %{ constraint(ALLOC_IN_RC(R0_regP)); match(iRegP); format %{ %} interface(REG_INTER); %} Proper way to fix it is either introduce missing operand declarations or remove problematic match rules.
27-11-2019