-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8364042: UnsafeMemoryAccess will not work with AOT cached code stubs #26511
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 adinn! A progress list of the required criteria for merging this PR into |
@adinn 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 43 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 |
Webrevs
|
I guess there's no way to test this contribution because the API has no customers, but you'll submit such testing as necessary in a later PR. |
Yes, that's right. This will be used by a PR I am working on to save and restore stubgenerator stubs. |
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.
looks fine to me
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.
Good.
@vnkozlov @ashu-mehra Thanks for the reviews! Integrating now. |
/integrate |
Going to push as commit a6fb87d.
Your commit was automatically rebased without conflicts. |
Array copy stubs may legitimately generate SEGV errors during copying. They rely on class UnsafeMemoryAccess to record and expose to the signal handler a table of address ranges within which a SEGV should be dealt with by redirecting execution to an associated handler address. The handler address may lie within the same stub or may default to an independent entry belonging to a specific, non-copy stub within the same blob. Normally entries are added to the table as a side-effect of generating the stub.
This patch implements the preliminary steps needed to enable save and restore of the UnsafeMemoryAccess table entries alongside with their associated AOT compiled copy stubs. It adds the common entry to the entry declarations list so it can be saved to the AOT cache during the assembly phase and reloaded, relocated and installed as the table default entry during a production run. It also implements an API that allows table entries associated with a given stub to be identified and saved during an assembly run, and retrieved, relocated and restored to the table during a production run.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26511/head:pull/26511
$ git checkout pull/26511
Update a local copy of the PR:
$ git checkout pull/26511
$ git pull https://git.openjdk.org/jdk.git pull/26511/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26511
View PR using the GUI difftool:
$ git pr show -t 26511
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26511.diff
Using Webrev
Link to Webrev Comment