Skip to content

(0.29.1) Avoid combining a regular type bound with a ClassObject location in VP - #129

Merged
0xdaryl merged 3 commits into
eclipse-openj9:v0.29.1-releasefrom
jdmpapin:vp-type-intersect-location-v0.29.1
Oct 26, 2021
Merged

0xdaryl merged 3 commits into
eclipse-openj9:v0.29.1-releasefrom
jdmpapin:vp-type-intersect-location-v0.29.1

Conversation

@jdmpapin

Copy link
Copy Markdown
Contributor

This is just eclipse-omr/omr#6208 cherry-picked onto v0.29.1-release. The diff should be identical to the diff in that PR

Fixes eclipse-openj9/openj9#13167

This logic was repeated for both VPResolvedClass and VPFixedClass, and
conspicuously missing from VPUnresolvedClass.

(cherry picked from commit 6be9456)
Any value known to satisfy the VPClassType constraint is an object, so
it must be a reflective object rather than a VM-internal representation.

(cherry picked from commit 85d2e95)
...as the intersection of the two constraints. If the type is not
already known to be a ClassObject, then bundling it into a VPClass with
a ClassObject location will incorrectly change the meaning of the type
constraint.

(cherry picked from commit d4ba4d4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants