-
Bug
-
Resolution: Fixed
-
P3
-
18, 19
-
b11
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8284427 | 18.0.2 | Tobias Hartmann | P3 | Resolved | Fixed | b03 |
C1 handles unresolved dynamic constants by performing constant resolution at runtime and then putting the constant value into the generated code by patching it. But it treats the not-yet-resolved value as a pure constant without any side effects. It's not the case for dynamic constants which are produced by a user-defined bootstrap method and there are no guarantees that it doesn't have any side effects.
- backported by
-
JDK-8284427 C1: Missing side effects of dynamic constant linkage
- Resolved
- relates to
-
JDK-8280473 CI: Support unresolved JVM_CONSTANT_Dynamic constant pool entries
- Resolved
-
JDK-8282218 C1: Missing side effects of dynamic class loading during constant linkage
- Resolved
- links to
-
Commit openjdk/jdk18u/7ebdcf56
-
Commit openjdk/jdk/93320717
-
Review openjdk/jdk18u/88
-
Review openjdk/jdk/7557
(2 links to)