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
8272791: java -XX:BlockZeroingLowLimit=1 crashes after 8270947 #8756
Conversation
|
@theRealAph 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. |
Webrevs
|
Change the lower limit of the range of the BlockZeroingLowLimit system flag. |
OK. |
Why not just do:
? |
@@ -4855,7 +4855,7 @@ address MacroAssembler::zero_words(Register ptr, Register cnt) | |||
// r10, r11, rscratch1, and rscratch2 are clobbered. | |||
address MacroAssembler::zero_words(Register base, uint64_t cnt) | |||
{ | |||
guarantee(zero_words_block_size < BlockZeroingLowLimit, | |||
guarantee(wordSize <= BlockZeroingLowLimit, |
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.
Surely, this guarantee
would now never fire? Maybe we should demote it to assert
to protect from accidental range error. There is no need to pay the price in release bits, I think.
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.
True.
@theRealAph This change now passes all automated pre-integration checks. 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 128 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.
|
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.
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.
Still good.
/integrate |
Going to push as commit e17118a.
Your commit was automatically rebased without conflicts. |
@theRealAph Pushed as commit e17118a. |
This is an assertion failure caused by setting
BlockZeroingLowLimit
<wordSize
.I believe there was some confusion when writing this code about whether
BlockZeroingLowLimit
should be in words or bytes, and it makes no sense for it to be less than a single word. If anyone ever tried to use a parameter < 8, it triggers an assertion.This patch does two things. Firstly, it corrects a
guarantee
which erroneously usedzero_words_block_size
rather thanwordSize
. The value of both of these is 8, so it doesn't change anything in the generated code. Secondly, it clips theBlockZeroingLowLimit
so that it doesn't trigger the assertion.Perhaps it would be better to change the lower limit to 8 instead of this silent correction. There is no backward compatibility issue here, because any attempt to set
BlockZeroingLowLimit
< 8 in the past would have exited the VM with an error, so I don't believe a CSR is warranted if we do change the allowable range.So, which should it be? Change the lower limit of the range of the
BlockZeroingLowLimit
system flag, or allow 1 still to be used and silently fix it? Opinions welcome.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8756/head:pull/8756
$ git checkout pull/8756
Update a local copy of the PR:
$ git checkout pull/8756
$ git pull https://git.openjdk.java.net/jdk pull/8756/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8756
View PR using the GUI difftool:
$ git pr show -t 8756
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8756.diff