Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P4
Fix Version/s: 18
Affects Version/s: 11, 15, 17, 18
Component/s: hotspot
Labels:

Subcomponent:
compiler
Resolved In Build:
b06
CPU:

generic
OS:

generic

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8270757	17.0.1	Severin Gehwolf	P4	Resolved	Fixed	b03
JDK-8270371	17	Severin Gehwolf	P4	Resolved	Fixed	b31
JDK-8270546	11.0.13-oracle	Tobias Hartmann	P4	Resolved	Fixed	b03
JDK-8270311	11.0.13	Severin Gehwolf	P4	Resolved	Fixed	b01

~~JDK-8225810~~ updated JVMCI. It also included a fix to MetaUtil.java so as to properly handle Java type names for generated lambda classes. However, whether or not that fix is present isn't covered in tests as far as I can see.

Let's add a test case so that this doesn't regress. The fix is actually needed to generate proper debuginfo for Graal VM CE builds for classes including lambda expressions.

backported by

JDK-8270311 [TESTBUG] Add coverage for jvmci ResolvedJavaType.toJavaName() for lambdas

Resolved

JDK-8270371 [TESTBUG] Add coverage for jvmci ResolvedJavaType.toJavaName() for lambdas

Resolved

JDK-8270546 [TESTBUG] Add coverage for jvmci ResolvedJavaType.toJavaName() for lambdas

Resolved

JDK-8270757 [TESTBUG] Add coverage for jvmci ResolvedJavaType.toJavaName() for lambdas

Resolved

relates to

JDK-8270196 [11u] [JVMCI] JavaType.toJavaName() returns incorrect type name for lambdas

Resolved

JDK-8225810 Update JVMCI

Resolved

links to

Commit openjdk/jdk11u-dev/23918db4

Commit openjdk/jdk17/d32e42cd

Commit openjdk/jdk/6a9bc108

Review openjdk/jdk11u-dev/123

Review openjdk/jdk17/246

Review openjdk/jdk/4746

(1 relates to, 6 links to)

Assignee:: Severin Gehwolf

Reporter:: Severin Gehwolf

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2021-07-09 08:21

Updated:: 2021-07-19 14:17

Resolved:: 2021-07-12 01:26

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates