You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.
It doesn’t need to. It’s already fully specified without that implication. Instructions can appear in multiple unrelated extensions, so either depending on Zvfhmin or not depending on it is valid.
Note also that Zfh doesn’t depend on Zfhmin; those two are analogously independent.
I was thinking of this because the Zve* extensions seems to have the implications to its subset (e.g. zve32f implies zve32x), and Zvfhmin is a proper subset of zvfh.
Is there a reason behind this asymmetry?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just noticed that 18.5. Zvfh: Vector Extension for Half-Precision Floating-Point mentions
Should there be an implication for Zvfh to zvfhmin?
The text was updated successfully, but these errors were encountered: