RFR: 8369573: Add missing compile commands help documentation for the signature part of method patterns

Daniel Lundén dlunden at openjdk.org
Thu Oct 16 12:29:30 UTC 2025


On Thu, 16 Oct 2025 08:23:10 GMT, Roberto Castañeda Lozano <rcastanedalo at openjdk.org> wrote:

>>> 2) in the context of Java, a "signature" tends to refer to the parameter types only, excluding return type
>> 
>> Additionally, the method signature also includes the method name itself (unlike the method descriptor). From the Java 25 spec:
>> 
>>> 8.4.2 Method Signature
>>> Two methods or constructors, M and N, have the same signature if they have the
>>> same **name**, the same type parameters (if any) (§8.4.4), and, after adapting the
>>> formal parameter types of N to the type parameters of M, the same formal parameter
>>> types.
>
>> > 2. in the context of Java, a "signature" tends to refer to the parameter types only, excluding return type
>> 
>> Additionally, the method signature also includes the method name itself (unlike the method descriptor). From the Java 25 spec:
>> 
>> > 8.4.2 Method Signature
>> > Two methods or constructors, M and N, have the same signature if they have the
>> > same **name**, the same type parameters (if any) (§8.4.4), and, after adapting the
>> > formal parameter types of N to the type parameters of M, the same formal parameter
>> > types.
> 
> This also raises the question about the usefulness of matching method return types, but that's out of the scope of this RFE.

@robcasloz: Now updated from "signature" to "descriptor" (instead of "method descriptor", for brevity).

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

PR Comment: https://git.openjdk.org/jdk/pull/27818#issuecomment-3410660415


More information about the hotspot-compiler-dev mailing list