Skip to content
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.

Implication for zvfh #885

Open
eopXD opened this issue Jun 1, 2023 · 2 comments
Open

Implication for zvfh #885

eopXD opened this issue Jun 1, 2023 · 2 comments

Comments

@eopXD
Copy link
Contributor

eopXD commented Jun 1, 2023

Just noticed that 18.5. Zvfh: Vector Extension for Half-Precision Floating-Point mentions

The Zvfh extension depends on the Zve32f and Zfhmin extensions.

Should there be an implication for Zvfh to zvfhmin?

@aswaterman
Copy link
Collaborator

aswaterman commented Jun 1, 2023

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.

@eopXD
Copy link
Contributor Author

eopXD commented Jun 2, 2023

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants