-
Notifications
You must be signed in to change notification settings - Fork 70
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
[herd]Modeling the X relation and how the Lr instruction is represented in riscv.cat #1210
Comments
Hi @curious-whq. Something looks wrong in your message: the executed test (ISA03+SB02) is not the test that is presented (ISA03+SIMPLE). |
@maranget
I sincerely apologize for any confusion I have caused, but I still genuinely hope to receive your guidance. Thank you in advance once again! |
Hi @curious-whq . To answer your questions:
This should explain your results. Notice that your test
This is how herd7 is operating. I am not completely comfortable about how this use of the |
Notice that PR #576 is still not merged yet. |
Dear Authors,
Sorry for interrupting you here. I am a newcomer to Herd, I'm encountering some puzzling errors while using herd7 to test litmus tests. I would like to present for your help:
I modified the riscv.cat file and tested it using litmus test.
For riscv.cat, I added two PPOs: r14 = [R];po;[X], r15 = [X];po;[W] and tested it using the following litmus test.
The results are as follows
But when I change r14 = [R];po;[Sc], r15 = [Sc];po;[W] the result is as follows
I don't understand the difference between X and Sc, and I'm also confused about why X would react to AMO instructions?And when I replace X with Sc, it seems that it no longer recognizes the Sc instruction either?
I would like to know where I can find the relations that can be used in RISC-V. Also, how is the Lr instruction represented in riscv.cat?
It would be sincerely appreciated if any comments or guidance could be provided. Thank you in advance for your time and great patience!
Yours sincerely,
Haoqi
The text was updated successfully, but these errors were encountered: