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
There's no definition of Zfhmin, and yet it's a valid extension.
Should Zfh imply Zfhmin, and so FLH, FSH, FMV.X.H, FMV.H.X, FCVT.S.H, FCVT.H.S etc. would be defined as Zfhmin, not as Zfh?
If so that would affect the isa-spec.
The profiles (RVA22, RVA23) require Zfhmin and not Zfh, so the definition doesn't fit with RISC-V opcodes.
More generally it would be useful to have a configuration for all of the mandatory extensions for RVA22, RVA23 so that we can just read them all in one, instead of finding problems like this one at a time.
I'm anticipating the same same problem with Zvfh/Zvfhmin
The text was updated successfully, but these errors were encountered:
tariqkurd-repo
changed the title
definition for Zfhmin?
why is there no definition for Zfhmin?
May 16, 2024
Seems like a fine improvement if you want to pursue it.
As to why it is the way it is, I think the answer is that many downstream tools that consume output from this repo just want all of the encoding information and don't care about how it's partitioned into extensions.
There's no definition of Zfhmin, and yet it's a valid extension.
Should Zfh imply Zfhmin, and so FLH, FSH, FMV.X.H, FMV.H.X, FCVT.S.H, FCVT.H.S etc. would be defined as Zfhmin, not as Zfh?
If so that would affect the isa-spec.
The profiles (RVA22, RVA23) require Zfhmin and not Zfh, so the definition doesn't fit with RISC-V opcodes.
More generally it would be useful to have a configuration for all of the mandatory extensions for RVA22, RVA23 so that we can just read them all in one, instead of finding problems like this one at a time.
I'm anticipating the same same problem with Zvfh/Zvfhmin
The text was updated successfully, but these errors were encountered: