On Wed, 22 Apr 2026 12:02:15 GMT, Alan Bateman <[email protected]> wrote:
>> Hello David, yesterday I went looking for those options in the `java` man >> page and JVM technical documentation at: >> >> https://docs.oracle.com/en/java/javase/26/docs/specs/man/java.html >> https://docs.oracle.com/en/java/javase/26/vm/java-virtual-machine-technology-overview.html >> >> But it isn't listed in either of those. Are there any other places you >> suggest looking at? > > Somewhat related is that BytecodeVerificationLocal's "doc" is "Enable the > Java bytecode verifier for local classes". I assume it means the boot loader > rather than "local classes". Hello Alan, I went through the history of this diagnostic option and it looks like its description and name have been using "local", "remote" ever since these options were introduced decades back. As for the implementation, you are right, "local" here appears to mean "bootstrap classloader": // This method determines whether we run the verifier and class file format checking code. bool Verifier::should_verify_for(oop class_loader) { return class_loader == nullptr ? BytecodeVerificationLocal : BytecodeVerificationRemote; } Looking at the usages and code comments for these functions, I think someone other than me who's more familiar with these options might have to decide whether it's worth creating a JBS issue to clean up the description and code comments of these `BytecodeVerificationLocal`/`BytecodeVerificationRemote` options. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30877#discussion_r3128779703
