Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downgrade isIndexableDataAddrPresent to BOOLEAN #20804

Merged

Conversation

amicic
Copy link
Contributor

@amicic amicic commented Dec 10, 2024

Effectively this was already a boolean, just taking more space than necessary. Thus compiler will be able to better pack 2 consecutive booleans (isIndexableDataAddrPresent and
isVirtualLargeObjectHeapEnabled)

Effectively this was already a boolean, just taking more space than
necessary. Thus compiler will be able to better pack 2 consecutive
booleans (isIndexableDataAddrPresent and
isVirtualLargeObjectHeapEnabled)

Signed-off-by: Aleksandar Micic <[email protected]>
@amicic
Copy link
Contributor Author

amicic commented Dec 10, 2024

jenkins test stability zLinux jdk21

@amicic
Copy link
Contributor Author

amicic commented Dec 10, 2024

jenkins compile aix,win jdk8

@amicic
Copy link
Contributor Author

amicic commented Dec 10, 2024

@TobiAjila realized I misspelled sanity in 'jenkins test stability zLinux jdk21'
leaving up to you if you want to add any other testing on top of compiles

@tajila
Copy link
Contributor

tajila commented Dec 10, 2024

Im happy with just compiles

@dmitripivkine dmitripivkine merged commit 10564ae into eclipse-openj9:master Dec 11, 2024
4 of 6 checks passed
@@ -5514,7 +5514,7 @@ typedef struct J9VMThread {
UDATA contiguousIndexableHeaderSize;
UDATA discontiguousIndexableHeaderSize;
#if defined(J9VM_ENV_DATA64)
UDATA isIndexableDataAddrPresent;
BOOLEAN isIndexableDataAddrPresent;
Copy link
Contributor

@keithc-ca keithc-ca Jan 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AuxFieldInfo29.dat should have been updated to be consistent with this change.

However, this may cause problems for DDR accessing older system dumps, particularly for big-ending systems if UDATA and BOOLEAN have different sizes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see this was reverted by #20816 (without explanation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants