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

Remove Section on non-idempotent memory handling #37

Closed
christian-herber-nxp opened this issue Jul 3, 2024 · 0 comments · Fixed by #38
Closed

Remove Section on non-idempotent memory handling #37

christian-herber-nxp opened this issue Jul 3, 2024 · 0 comments · Fixed by #38

Comments

@christian-herber-nxp
Copy link
Collaborator

from @ved-rivos:

Section 2.6

"Software should only use these instructions on non-idempotent memory regions when software can tolerate the required memory accesses being issued repeatedly in the case that they cause exceptions." This text is a bit misleading as the region cannot be non-idempotent if repeated accesses can be tolerated. That said this whole section can be deleted as the allowance of redoing the memory access has been discussed in earlier sections at length and this property is not different than the existing FLD/FSD for RV32.

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

Successfully merging a pull request may close this issue.

1 participant