-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8171508: Remove -Dsun.java.launcher.is_altjvm option #24310
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
…m option after 8066474
👋 Welcome back ccheung! A progress list of the required criteria for merging this PR into |
@calvinccheung 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 178 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 |
/label add hotspot-runtime |
@calvinccheung |
Webrevs
|
Hi @calvinccheung, I thought we planned on removing altjvm handling altogether? See mail thread https://mail.openjdk.org/pipermail/hotspot-runtime-dev/2017-April/023205.html |
But we got rid of the |
I've pushed a commit which removes altjvm handling in JVM. There's small piece of code in the java launcher (java.c) which I didn't remove because:
|
I've removed the processing regarding the slashes and the |
This issue should be renamed "Remove -Dsun.java.launcher.is_altjvm option". That requires a CSR request to be filed. Once again for the record -XXaltjvm has nothing to do with the -Dsun.java.launcher.is_altjvm option. https://mail.openjdk.org/pipermail/hotspot-runtime-dev/2017-April/023241.html Removal of -XXaltjvm would also need a CSR request. |
I filed a draft CSR JDK-8353678. |
How does the gtest launcher work with these changes? There the libjvm.so is in a completely different place to the JDK. ?? |
Also as discussed offline picking up JAVA_HOME from the environment is not the right thing to do in general. It only worked with -Dsun.java.launcher.is_altjvm because we ensured we set JAVA_HOME when using the property. |
gtest launcher sets the |
Can you update the PR description to clarify what is now being done please Calvin. |
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.
So basically now we have removed the -Dsun.java.launcher.is_altjvm
option and replaced its use with gtest by the use of the executing_unit_tests
functionality. Okay.
A few minor requests. Thanks.
Updated PR description. |
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.
Are the Posix variants all identical? If yes, can we move this to os::posix.cpp? If not, what are the differences?
AIX has a different dll lookup mechanism, but otherwise these should be pretty much identical. Windows also only really differs in the lookup mechanism. Maybe new RFE to refactor these and share some code? |
Okay. The code could also be simpler if it were to use stringStream, spanned over the caller-provided buffer. No character counting and truncation handling needed then (but we would need to add truncation detection to stringStream, but that is really easy). |
I agree with David about doing the refactoring in a new RFE. I've simplified the code by using stringStream as you suggested. I didn't add truncation detection to stringStream (which I think could be done in another RFE). However, I added an assert in |
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.
Nice, this looks good to me. Thank you.
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 okay. Some additional possible cleanup now you are using the stringStream.
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. Thanks
Thanks @tstuefe, @dholmes-ora for the review. /integrate |
Going to push as commit 7680f70.
Your commit was automatically rebased without conflicts. |
@calvinccheung Pushed as commit 7680f70. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The
-Dsun.java.launcher.is_altjvm
option is only used in the gtest launcher and has no relationship with the similarly named-XXaltjvm
option. The gtest launcher also sets the-XX:+ExecutingUnitTests
option. This RFE involves removing the-Dsun.java.launcher.is_altjvm
option, capturing the-XX:+ExecutingUnitTests
option in Arguments::process_sun_java_launcher_properties() so that the os::jvm_path() can check if the option is set before using JAVA_HOME setting.Passed tiers 1 - 3 testing.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24310/head:pull/24310
$ git checkout pull/24310
Update a local copy of the PR:
$ git checkout pull/24310
$ git pull https://git.openjdk.org/jdk.git pull/24310/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24310
View PR using the GUI difftool:
$ git pr show -t 24310
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24310.diff
Using Webrev
Link to Webrev Comment