-
Notifications
You must be signed in to change notification settings - Fork 219
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
8288719: [arm32] SafeFetch32 thumb interleaving causes random crashes #1577
Conversation
👋 Welcome back snazarki! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issues from the original commit. |
Webrevs
|
Please use links to JBS, not to Azul-internal bug trackers (also I'm too lazy to lookup 8285675 manually :). |
Oops! Updated the link to JBS |
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.
Okay.
Note that the test needs to be executed on a machine where gcc uses mthumb by default, IIRC.
OTOH the patch is so basic that this is fine even without testing.
Can you please do / isuue add JDK-8285675 as this subsumes that change. |
/issue add 8285675 |
@snazarkin |
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout JDK-8284997
git fetch https://git.openjdk.org/jdk17u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
@snazarkin 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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
Got the push approval. /integrate |
Going to push as commit 8c1a5bc. |
@snazarkin Pushed as commit 8c1a5bc. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi!
This is follow up for #1557. The backport is not clean since JDK-8285675 was skipped intentionally.
Tested with gtest:all on RPi3
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1577/head:pull/1577
$ git checkout pull/1577
Update a local copy of the PR:
$ git checkout pull/1577
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1577/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1577
View PR using the GUI difftool:
$ git pr show -t 1577
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1577.diff
Webrev
Link to Webrev Comment