8383990: Remove exception code filters from Windows AArch64 safefetch handler#31158
8383990: Remove exception code filters from Windows AArch64 safefetch handler#31158swesonga wants to merge 2 commits into
Conversation
|
👋 Welcome back swesonga! A progress list of the required criteria for merging this PR into |
|
@swesonga 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 49 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@dholmes-ora, @TheShermanTanker) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
The total number of required reviews for this PR has been set to 2 based on the presence of this label: |
Webrevs
|
dholmes-ora
left a comment
There was a problem hiding this comment.
It looks like exception_code is now unused and so can be removed from the signature.
Also this code has a section for _LP64 but as far as I can see the only call to handle_safefetch is from a section for _M_ARM64 - so the LP64 code seems dead as well.
handle_safefetch (defined in src/hotspot/share/runtime/safefetch_static.hpp) is a function used by the other platforms as well. I left it unchanged to avoid special-casing it for windows-aarch64
_LP64 is defined for all 64-bit CPUs in make/autoconf/flags-cflags.m4 so that code is not dead. It is tested by the SafeFetchN_with_page_guard_protection gtest |
Hmmm okay. It is declared in a shared header file but as far as I can see there are no callers from shared code. It seems to exist in the shared file to simplify the include process even though it is only used by platform-specific code and so could be declared in a platform specific header.
Doh! Sorry yes my brain read that referring to x86_64. |
|
/integrate |
|
/sponsor |
|
Going to push as commit f66380e.
Your commit was automatically rebased without conflicts. |
JDK-8383541: Safefetch should return the error value when accessing pages protected with PAGE_GUARD on windows-aarch64 added a handler for guard pages specifically. However, @mo-beck has pointed out that we can actually remove the list of exceptions altogether to future-proof the safefetch implementation since it uses a LDR instruction whose PC is known and checked for by handle_safefetch. The gtests added in JDK-8383541 still pass with this change.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31158/head:pull/31158$ git checkout pull/31158Update a local copy of the PR:
$ git checkout pull/31158$ git pull https://git.openjdk.org/jdk.git pull/31158/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 31158View PR using the GUI difftool:
$ git pr show -t 31158Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31158.diff
Using Webrev
Link to Webrev Comment