[lworld] RFR: 8367935: [lworld] Rename ACC_STRICT in the JVM according to strict fields JEP [v2]

Roger Riggs rriggs at openjdk.org
Wed Feb 4 21:27:42 UTC 2026


On Wed, 4 Feb 2026 17:36:23 GMT, Matias Saavedra Silva <matsaave at openjdk.org> 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.
>
> Matias Saavedra Silva has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Remove strict_init from Modifier

src/java.base/share/classes/java/lang/invoke/MemberName.java line 396:

> 394:     public boolean isStrict() {
> 395:         return Modifier.isStrict(flags);
> 396:     }

It seems that this `Membername.isStrict()` is unused, can it/should it be removed.

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

PR Review Comment: https://git.openjdk.org/valhalla/pull/2025#discussion_r2766040475


More information about the valhalla-dev mailing list