On Tue, 3 Feb 2026 20:21:48 GMT, Matias Saavedra Silva <[email protected]>
wrote:
> Strict initialization is now indicated with the access flag `ACC_STRICT_INIT`
> in the JVMS and the VM implementation should follow. `ACC_STRICT` is
> currently used as a method modifier for strict floating-point semantics so
> this refactor will help to make both modifiers distinct. VM and Java code has
> to be updated to use the correct modifier. Verified with tier x-y tests.
src/java.base/share/classes/java/lang/invoke/MemberName.java line 398:
> 396: /** Utility method to query the modifier flags of this member. */
> 397: public boolean isStrictInit() {
> 398: return Modifier.isStrictInit(flags);
Let's do `allFlagsSet(ClassFile.ACC_STRICT_INIT);` and remove the stuff from
`Modifier`. The `ACC_STRICT_INIT` flag is NOT a source modifier.
src/java.base/share/classes/java/lang/reflect/Modifier.java line 1:
> 1: /*
Please drop all changes to this file.
-------------
PR Review Comment:
https://git.openjdk.org/valhalla/pull/2025#discussion_r2761402633
PR Review Comment:
https://git.openjdk.org/valhalla/pull/2025#discussion_r2761403931
