-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8311976: Inconsistency in usage of CITimeVerbose to generate compilation logs #14880
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
…ion logs Signed-off-by: Ashutosh Mehra <asmehra@redhat.com>
|
👋 Welcome back ashu-mehra! A progress list of the required criteria for merging this PR into |
|
@ashu-mehra 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 /label pull request command. |
|
@ashu-mehra, can you show output before and after this changes? It would be nice to see what you are fixing. |
|
First change is in the amount of information in the C1 compilation log. Before the fix with -XX:+LogCompilation (irrespective of CITimeVerbose), one example of each C1 and C2 compilation: Note that for C1 all phases are displayed, but not for C2. To include the phase information for C2, After the fix with -XX:+LogCompilation, example of C1 compilation: and with -XX:+LogCompilation -XX:+CITimeVerbose example of C1 compilation: Note that phase information for C1 compilation is now displayed only with The other change is in the Before the fix: After the fix: This makes it easier to trace the start and end of a phase even when there are sub-phases in between. |
vnkozlov
left a comment
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. Thank you for showing output change.
|
@ashu-mehra 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 85 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 (@vnkozlov, @TobiHartmann) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@vnkozlov thanks for reviewing it. |
|
Looking for one more reviewer for this patch. |
TobiHartmann
left a comment
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 to me.
|
/integrate |
|
@ashu-mehra |
|
/sponsor |
|
Going to push as commit 3e8f1eb.
Your commit was automatically rebased without conflicts. |
|
@tstuefe @ashu-mehra Pushed as commit 3e8f1eb. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this PR for controlling timing information of C1 compilation phases using CITimeVerbose option, same as for C2 compilations.
I also took this opportunity to fix some other minor issues with logging:
Compilation::current(). For this reason I moved the statementPhaseTraceTime timeit(_t_compile)after the call to_env->set_compiler_data(this);.Compilation::current()in PhaseTraceTime constructor.phase_donetag and ignores all other parameters passed to it. This was due to a bug inxmlStream::va_donewhich is also fixed in here.I felt these are all minor fixes so I clubbed them together. here If it feel inappropriate I can pull them in their own PRs.
Testing: GHA testing passed
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14880/head:pull/14880$ git checkout pull/14880Update a local copy of the PR:
$ git checkout pull/14880$ git pull https://git.openjdk.org/jdk.git pull/14880/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14880View PR using the GUI difftool:
$ git pr show -t 14880Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14880.diff
Webrev
Link to Webrev Comment