On Thu, 23 Apr 2026 06:33:14 GMT, Jaikiran Pai <[email protected]> wrote:
>> 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.
Yeah this is historical naming - just squint tightly when reading it. :)
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/30877#discussion_r3128938229
