RFR: 8266530: HotSpot changes for JEP 306 [v2]

[Harold Seigel]

On Thu, 6 May 2021 17:40:27 GMT, Joe Darcy <darcy at openjdk.org> wrote:

>> Please review these VM changes in support of JEP 306: Restore Always-Strict Floating-Point Semantics.
>> 
>> JEP 306 is considering the following changes to the JVMS: 
>> 
>> 1) Require "strict" floating-point evaluation in all circumstances.
>> 2) For class file version 61 and higher, undefine ACC_STRICT, moving that bit position back to undefined for methods. For class file versions, 46 through, ACC_STRICT would remain a defined modifier.
>> 
>> Since all floating-point evaluation is done strictly, a modifier bit is not needed to indicate this anymore. There are a few mandated modifier checks when ACC_STRICT is defined, such as not allowing an "abstract strictfp" method. These checks in classFileParser are now conditional on the class file version.
>> 
>> The tests verify  "abstract strictfp" triggers a ClassFormatError  for version 60 and does not trigger an error or exception for version 61. (As an undefined bit in version 61, the VM is supposed to ignore it.)
>> 
>> FYI, the javac and core libs portions of JEP 306 are out for review under https://github.com/openjdk/jdk/pull/3831.
>> 
>> The HotSpot and javac/core libs parts of JEP 306 are independent in that neither relies on the other:
>>  * javac will not output class files which expose the difference in class parsing behavior; the ACC_STRICT modifier will not be set in any version 61 class file emitted by javac.
>>  *  since HotSpot already does all floating-point evaluation strictly, no changes are needed to support strict evaluation.
>
> Joe Darcy has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Respond to review feedback.

Additional changes may be needed to these hotspot files that contain ACC_STRICT:
cpu/x86/templateTable_x86.cpp:      __ testl(rcx, JVM_ACC_STRICT);
cpu/x86/templateTable_x86.cpp:      __ testl(rcx, JVM_ACC_STRICT);
share/ci/ciFlags.hpp:  bool is_strict               () const { return (_flags & JVM_ACC_STRICT                    ) != 0; }
share/include/jvm_constants.h:                                         JVM_ACC_STRICT | \
share/utilities/accessFlags.hpp:  bool is_strict      () const         { return (_flags & JVM_ACC_STRICT      ) != 0; }

Also, there are multiple hotspot tests that contain ACC_STRICT.

-------------

PR: https://git.openjdk.java.net/jdk/pull/3891