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

No testing of memory hazards #498

Open
jordancarlin opened this issue Feb 27, 2025 · 0 comments
Open

No testing of memory hazards #498

jordancarlin opened this issue Feb 27, 2025 · 0 comments

Comments

@jordancarlin
Copy link
Member

As far as I can tell, the only hazards we check for right now are with the integer and floating point registers. If the idea is to test RAW, WAR, and WAW hazards, then we should also be checking consecutive loads/stores to the same address. riscvISACOV came with a built in function for this (check_mem_hazards) similar to the check_gpr_hazards that we are already using. All load and store instructions should be updated to include this as a coverpoint.

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

1 participant