Skip to content
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

frm is illegal value , a vector fp inst raise illegal inst but it still will make vs dirty #1646

Open
xinyuwang-starfive opened this issue Apr 18, 2024 · 1 comment

Comments

@xinyuwang-starfive
Copy link
Contributor

for vector fp inst,now spike check require vector first and then require_vector first and then requre frm。
in require vector it will dirty vs。
so if frm is illegal now it will make dirty and will dirty vs。
#define VI_VFP_COMMON \ require_fp; \ require((P.VU.vsew == e16 && p->extension_enabled(EXT_ZVFH)) || \ (P.VU.vsew == e32 && p->extension_enabled('F')) || \ (P.VU.vsew == e64 && p->extension_enabled('D'))); \ require_vector(true); \ require(STATE.frm->read() < 0x5); \
i check spec and not found the detail about how to do it.
can you tell me Whether it meets expectations?

@aswaterman
Copy link
Collaborator

I think this is technically not a bug; implementations are allowed to change the state from clean or initial to dirty for any reason. However, I agree it is cleaner not to dirty the state in the event of an illegal-instruction exception. I’ll leave others to comment on the implementation details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants