8262952: [macos_aarch64] os::commit_memory failure #3865
On x86_64 macOS the following sequence works just fine:
however, on aarch64 macOS it fails.
We fix the test itself to explicitly ask for executable memory when reserving it since it later commits it as executable.
The text was updated successfully, but these errors were encountered:
@gerard-ziemski This change now passes all automated pre-integration checks.
After integration, the commit message for the final commit will be:
At the time when this comment was updated there had been 191 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.
Talking about "exec" permission of the memory in
I'm sure there must be a reason, that I don't know, but why do we need it to be of "PROT_READ"? Java2Demo, for example, seems to run fine without the "read" permission on it, i.e.:
@gerard-ziemski Since your change was applied there have been 196 commits pushed to the
Your commit was automatically rebased without conflicts.
Pushed as commit fadf580.