Check if instanceDescription is an immediate value in loop #15713
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a case where the number of object slots are greater than the number of bits in a word and
instanceDescription
is used as an immediate value instead of a pointer, such as when the class doesn't have any references. We need to break the loop in this case beforeinstanceDescription
is dereferenced as a pointer.This fixes
openj9-jit-xopt/issues/529
Thanks to Henry @hzongaro for tracking down the issue to hasReferneces change #10651
Signed-off-by: Annabelle Huo Annabelle.Huo@ibm.com