-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8310053: VarHandle and slice handle derived from layout are lacking alignment check #14475
Conversation
👋 Welcome back jvernee! A progress list of the required criteria for merging this PR into |
@JornVernee The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
// (J, ...) -> J to (J, J, ...) -> J | ||
// i.e. new coord is prefixed. Last coord will correspond to innermost layout | ||
handle = MethodHandles.collectCoordinates(handle, 1, collector); | ||
handle = MethodHandles.collectCoordinates(handle, 1, offsetHandle()); |
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.
nice simplification!
|
||
String expectedMessage = "Target offset incompatible with alignment constraints: " + struct.byteAlignment(); | ||
|
||
try { |
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.
Can assertThrows be used to simplify this pattern?
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.
Yeah. I thought assertThrows
was only a junit thing, but it looks like TestNG also has an expectThrows
which does the same and returns the thrown exception so that we can check the message.
@@ -380,6 +380,10 @@ default MethodHandle byteOffsetHandle(PathElement... elements) { | |||
* Additionally, the provided dynamic values must conform to bounds which are derived from the layout path, that is, | |||
* {@code 0 <= x_i < b_i}, where {@code 1 <= i <= n}, or {@link IndexOutOfBoundsException} is thrown. | |||
* <p> | |||
* The accessed address must be <a href="MemorySegment.html#segment-alignment">aligned</a> according to the {@linkplain |
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.
Very nice and clear!
Use expectThrows
I've switched to |
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.
Bonus points!
I'm wondering... for dereference path elements, we already perform a root layout check as part of the memory segment expansion - e.g. we use the target layout to resize the segment (and perform an alignment check). So in that case there would still be duplicate alignment checks. In such cases, we need to make sure that either (a) only the first var handle in the dereference chain gets the proper alignment adaptation on the input segment or that (b) they all do, but then we omit the alignment checks that are generated as part of calling VH::get on the address layout (but that might be harder to do, as that logic is shared). I think (a) is probably simplest - just have a boolean in the path which says whether a path is nested into some other path using a dereference and, if so, omit the alignment adaptation? |
That would be easy enough to do, we just check for |
minor javadoc fix add test for misaligned deref
I've gone ahead and implemented this. I also added a test to make sure that alignment checks still happen when using deref path elements. I also fixed a minor javadoc issue, in the doc for varHandle. It said that we checked the alignment of the accessed address, but we check the alignment of the base address (a term which is defined earlier). |
@JornVernee 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 69 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 e022e87.
Your commit was automatically rebased without conflicts. |
@JornVernee Pushed as commit e022e87. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk21 |
@JornVernee the backport was successfully created on the branch JornVernee-backport-e022e876 in my personal fork of openjdk/jdk21. To create a pull request with this backport targeting openjdk/jdk21:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk21:
|
Add missing alignment checks for the alignment constraint of the root layout of a VarHandle created through
MemoryLayout::varHandle
and a MethodHandleMemoryLayout::sliceHandle
.Testing:
jdk_foreign
test suiteProgress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14475/head:pull/14475
$ git checkout pull/14475
Update a local copy of the PR:
$ git checkout pull/14475
$ git pull https://git.openjdk.org/jdk.git pull/14475/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14475
View PR using the GUI difftool:
$ git pr show -t 14475
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14475.diff
Webrev
Link to Webrev Comment