[GR-48949] For instance objects, move the identity hashcode from the object header into the object. #7835
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.
For instance objects, it makes sense to move the identity hashcode from the object header into the object. If there are any gaps in the object layout, the identity hashcode can be placed in such a gap, which decreases memory usage. If there are no gaps, the identity hashcode is appended to the object, resulting in the same memory usage as before. So, this PR strictly reduces memory usage.
As a side effect, it is more likely that the Native Image field offsets are different from the offsets used by HotSpot. This makes it easier to diagnose and debug when a field offset computed at image build time is wrongly used at image run time.