-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 20
-
b24
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8298359 | 17.0.7-oracle | Tobias Hartmann | P4 | Resolved | Fixed | b01 |
| JDK-8297658 | 17.0.6 | Severin Gehwolf | P4 | Resolved | Fixed | b05 |
When ResolvedJavaMethod.getCodeSize returns a value > 0, it is currently possible for ResolvedJavaMethod.getCode to return null (i.e. when the declaring class is not linked) which has confused many JVMCI API users and led to subtle bugs. Experience has shown that a value > 0 means callers expect getCode to not return null. It's about time to conform to this reasonable expectation. If the declaring class is not linked, getCodeSize should return -1.
- backported by
-
JDK-8297658 [JVMCI] rationalize relationship between getCodeSize and getCode in ResolvedJavaMethod
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8297590 [TESTBUG] HotSpotResolvedJavaFieldTest does not run
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/b464cc2d
-
Commit
openjdk/jdk/37848a9c
-
Review
openjdk/jdk17u-dev/934
-
Review
openjdk/jdk/11147
(2 links to)