-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8358892: RISC-V: jvm crash when running dacapo sunflow after JDK-8352504 #25696
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
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back mli! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
@Hamlin-Li 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
|
Try this:
$ java -XX:-TieredCompilation Test This reduced test can reproduce the crash and cover both Edit: Here is a more simplified version of the test.
|
/solves JDK-8359045 /contributor add @RealFYang |
@Hamlin-Li |
@Hamlin-Li |
We need new implementation for BoolTest::ge/gt, because of NaN cases. It's done. |
Hi,
Hmm, I don't understand why your first commit (e5b06b5) won't work for NaN cases. I also changed my test a bit trying NaN cases and it still works if I use your first commit (e5b06b5).
|
I think the reason is the original assumption is not right about the behaviour of cmov_cmp_fp_ge/gt.
You can see failures when running new tests if revert back to first commit of implementation. |
Hi, I changed your test a bit and I see test failure on my linux-riscv64 platform (no Zicond).
$ make test TEST="test/hotspot/jtreg/compiler/c2/irTests/TestFPComparison2.java" JTREG="TIMEOUT_FACTOR=8"
|
Hi,
Can you help to review this patch?
Thanks!
Currently, this issue is only reproducible with Dacapo sunflow.
I tried to construct a simpler jtreg test to reproduce the issue, but can not find a way to do it till now, this task is tracked by https://bugs.openjdk.org/browse/JDK-8359045.
So, currently I can only verify the code by reviewing it.
Or maybe it's better to leave it until we find the test?
Progress
Issues
Contributors
<[email protected]>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25696/head:pull/25696
$ git checkout pull/25696
Update a local copy of the PR:
$ git checkout pull/25696
$ git pull https://git.openjdk.org/jdk.git pull/25696/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25696
View PR using the GUI difftool:
$ git pr show -t 25696
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25696.diff
Using Webrev
Link to Webrev Comment