-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8368950: RISC-V: fail to catch out of order declarations among dependent cpu extensions/flags #27572
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?
8368950: RISC-V: fail to catch out of order declarations among dependent cpu extensions/flags #27572
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. |
Hi,
Can you help to review this patch?
Background
In https://bugs.openjdk.org/browse/JDK-8352218, we introduced dependency among CPU extensions/flags. And to make sure it works, A needs to be declared before B in RV_FEATURE_FLAGS if B depends on A, for example, A is v, B is Zvfh. So in the pr an assert was introduced to make sure A is before B in RV_FEATURE_FLAGS.
But the assert does not work as expected, means if I move A below B in RV_FEATURE_FLAGS (check below for a simple patch, it's based on 7853415), it can not be caught by the assert.
If added following patch based on the above patch, we can find out what's going on, it will trigger the assert:
But I don't think we can rely on the address of different ext_x to determine their declaration order in RV_FEATURE_FLAGS, even if the patch above can catch it.
Fix
This patch reuses RVExtFeatureValue::_cpu_feature_index as dependent_index to check the declaration order is as expected.
Test
With the following patch, it will trigger the assert:
Thanks!
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27572/head:pull/27572
$ git checkout pull/27572
Update a local copy of the PR:
$ git checkout pull/27572
$ git pull https://git.openjdk.org/jdk.git pull/27572/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27572
View PR using the GUI difftool:
$ git pr show -t 27572
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27572.diff
Using Webrev
Link to Webrev Comment