-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8274293: Build failure on macOS with Xcode 13.0 as vfork is deprecated #5686
Conversation
👋 Welcome back xpbob! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
I think this looks okay but would be good for @RogerRiggs to also review.
@xpbob 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 23 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 (@AlanBateman, @tstuefe, @RogerRiggs) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
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.
The JDK change is fine. AFAICS we have used posix_spawn by default on MacOS since at least 2015, and vfork was not even an option on MacOS.
Wrt the hotspot portion, we now fall back to fork. I wonder what the footprint penalty is compared to vfork. os::fork_and_exec
gets used mainly by error reporting (-XX:OnError
=xxx), e.g. in OOM situations. We now may run into situations where error analysis tools are unable to spawn if the parent is too big. Maybe we should change os::fork_and_exec()
to use posix_spawn instead?
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.
.. I opened https://bugs.openjdk.java.net/browse/JDK-8274320 to track the proposed change of os::fork_and_exec() to posix_spawn. So I am fine with this change.
/integrate |
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 good, vfork is not/was not being used on Mac OS.
/sponsor |
/sponsor |
Going to push as commit 252aaa9.
Your commit was automatically rebased without conflicts. |
@DamonFool @xpbob Pushed as commit 252aaa9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@DamonFool The command |
remove vfork() on Darwin
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5686/head:pull/5686
$ git checkout pull/5686
Update a local copy of the PR:
$ git checkout pull/5686
$ git pull https://git.openjdk.java.net/jdk pull/5686/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5686
View PR using the GUI difftool:
$ git pr show -t 5686
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5686.diff