-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8310170: Use sp's argument to improve performance of outputStream::indent and remove SP_USE_TABS #14502
Conversation
👋 Welcome back jsjolen! A progress list of the required criteria for merging this PR into |
@jdksjolen 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. |
/label add hotspot-runtime |
@jdksjolen |
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.
Looks okay. I thought what would happen if _indentation < _position
, but sp()
seems to handle count < 0
fine.
@jdksjolen 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 250 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 |
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.
There's potentially a subtle difference in behaviour here if SP_USE_TABS were ever true - but as it is defined to be false there is no difference in practice. Maybe we should just cull the code related to SP_USE_TABS and not pretend we could do something different here?
Thanks.
Hi, Sorry for the slow response from me on this. @dholmes-ora, let's remove SP_USE_TABS in this PR. I'll change the ticket 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.
Good.
@@ -186,18 +186,9 @@ void outputStream::put(char ch) { | |||
write(buf, 1); | |||
} | |||
|
|||
#define SP_USE_TABS false | |||
|
|||
void outputStream::sp(int count) { | |||
if (count < 0) return; |
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.
Is this needed?
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 count < 0
check? Yes, as Shipilev mentioned:
Looks okay. I thought what would happen if _indentation < _position, but sp() seems to handle count < 0 fine.
So it's nice that we don't have to care at the call site.
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.
Ah, okay. Missed that.
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.
As an aside I was disappointed to discover that the indentation facility is far less useful than it might be. I had hoped you could set the indentation and then have all following log output indented, until you reset it. But indentation only happens when you explicitly call indent()
so you can't call e.g. val->print_on(stream)
and have the caller control indentation (without print_on
directly supporting it).
One structured concurrency test fails on GHA on Linux-x86. That can't be thanks to this patch. Integrating. /integrate |
Going to push as commit 92ca670.
Your commit was automatically rebased without conflicts. |
@jdksjolen Pushed as commit 92ca670. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
Please consider this small enhancement.
sp
takes a count argument, this was never used byindent
, let's just use it.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14502/head:pull/14502
$ git checkout pull/14502
Update a local copy of the PR:
$ git checkout pull/14502
$ git pull https://git.openjdk.org/jdk.git pull/14502/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14502
View PR using the GUI difftool:
$ git pr show -t 14502
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14502.diff
Webrev
Link to Webrev Comment