-
Notifications
You must be signed in to change notification settings - Fork 61
8299181: PaddingLayout unable to return byteAlignment value #766
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
Conversation
👋 Welcome back pminborg! A progress list of the required criteria for merging this PR into |
Webrevs
|
MemoryLayoutUtil.checkSize(size); | ||
return PaddingLayoutImpl.of(size); | ||
static PaddingLayout paddingLayout(long bitSize) { | ||
if (bitSize < 0 || bitSize % 8 != 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm not mistaken, this is the same check that should be applied when we call withBitAlignment
, right? It might be useful to consolidate (both impl-wise and doc-wise).
StructLayoutImpl.of(Stream.of(elements) | ||
.map(Objects::requireNonNull) | ||
.toList())); | ||
return wrapOverflow(() -> StructLayoutImpl.of(List.of(elements))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was Objects.requireNonNull dropped? I believe that NPE will be thrown deeper inside the implementation - which is why we had the eager check (to make stack trace more readable).
if (((alignmentBitCount & (alignmentBitCount - 1)) != 0L) || //alignment must be a power of two | ||
(alignmentBitCount < 8)) { //alignment must be greater than 8 | ||
throw new IllegalArgumentException("Invalid alignment: " + alignmentBitCount); | ||
private static long requirePowerOfTwoAndGreaterOrEqualToEight(long value) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this stay here, or be merged inside MemoryLayoutUtil? It seems the same as requireBitSizeValid
, except for the zero behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This method also checks if the parameter is an even power of two.
|
||
@Test | ||
public void testNullMember() { | ||
var illegalLayouts = new MemoryLayout[]{JAVA_INT, null, JAVA_INT}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is covered by TestNulls. That test will try to pass null values to all API methods accepting arrays, or collections, and will do so in an automatic fashion.
@minborg This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 180 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 477cc26.
Your commit was automatically rebased without conflicts. |
This PR proposes bit-aligning
PaddingLayout
to 8 by default as opposed to the current value of 1.More generally, the PR restricts
PaddingLayout
bit-alignment to non-negative values that are an even multiple of 8 (i.e. 0, 8, 16, ...). There are no mechanism to deriveVarHandle
objects for sub-byte access anyhow and trying to obtain a miss-alignedVarHandle
would throw an exception.If integrated, all
MemoryLayout
types would be byte-aligned.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/panama-foreign pull/766/head:pull/766
$ git checkout pull/766
Update a local copy of the PR:
$ git checkout pull/766
$ git pull https://git.openjdk.org/panama-foreign pull/766/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 766
View PR using the GUI difftool:
$ git pr show -t 766
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/panama-foreign/pull/766.diff