RFR: 8368331: ClassFile Signature parsing fails for type parameter with no supertype [v4]

[ExE Boss]

On Tue, 23 Sep 2025 19:10:17 GMT, Chen Liang <liach at openjdk.org> wrote:

>> Some type parameter declaration signatures in class and method generic signatures, such as `<T:R:>`, are valid per JVMS but are not accepted by either the ClassFile or the legacy core reflection parser. (Javac doesn't generate these because it always generates an Object upper bound) They can be constructed by the ClassFile API models. So it makes sense to support their parsing as supported by JVMS and our API model.
>
> Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 10 commits:
> 
>  - Fix bad test merge
>  - Merge branch 'master' of https://github.com/openjdk/jdk into fix/cf-typevar-parse
>  - Merge branch 'master' of https://github.com/openjdk/jdk into fix/cf-typevar-parse
>  - 8368331: ClassFile Signature parsing fails for type parameter with no supertype
>  - More fixes
>  - Fix bad docs and add more to clarify class type sig
>  - Merge branch 'master' of https://github.com/openjdk/jdk into fix/cf-classtypesig-factory-classdesc
>  - Fix links
>  - More bugs
>  - 8368050: Validation missing in ClassFile signature factories

The **JBS** issue should probably link to [JDK‑8351103].

[JDK‑8351103]: https://bugs.openjdk.org/browse/JDK-8351103

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

PR Comment: https://git.openjdk.org/jdk/pull/27439#issuecomment-3330928121