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
8253412: Unsupported GC options passed in JAVA_TOOL_OPTIONS are silently ignored #282
Conversation
|
@shipilev The following label will be automatically applied to this pull request: When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the |
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.
FLAG_IS_CMDLINE is often used as "FLAG_IS_USERSPECIFIED". So I have the feeling many (most?) uses of FLAG_IS_CMDLINE is semi-broken, given that options coming in through JAVA_TOOLS_OPTIONS and _JAVA_OPTIONS isn't considered part of the command-line.
Anyway, this change looks good to me.
@shipilev This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements After integration, the commit message will be:
Since the source branch of this PR was last updated there have been 16 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 automatic rebasing, please merge
|
/integrate |
@shipilev Since your change was applied there have been 16 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit a4affd5. |
See the reproducer in the bug itself. I think that happens because GCConfig checks only for FLAG_IS_CMDLINE, which is only from cmdline-originated flags. In this case, the flag comes from the environment variable. Maybe checking for
!FLAG_IS_DEFAULT
is better, as it captures all non-default origins.But them, instead of checking for
FLAG_IS_CMDLINE
, I think we can rely on the fact that allUse*GC
options arefalse
by default. So if any of such flags istrue
, it means something had selected the GC. This allows for some further simplification of the macro (although I am not sure if it was intended to be ever used to check-XX:-*
flags).Attention @pliden.
Testing:
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/282/head:pull/282
$ git checkout pull/282