Skip to content

Commit d33f3d8

Browse files
authored
Fix misquote in RVWMO Rules (riscv#1663)
* Fix misquote in RVWMO Rules Signed-off-by: Robert Balas <[email protected]> * Remove spurious closing bracket in RVWMO Rules --------- Signed-off-by: Robert Balas <[email protected]> Co-authored-by: bluew <[email protected]>
1 parent 0594e18 commit d33f3d8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/mm-eplan.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ visible memory). Any other hart will therefore observe the load as
239239
performing before the store.
240240

241241
Consider the <<litms_sb_forward>>. When running this program on an implementation with
242-
store buffers, it is possible to arrive at the final outcome a0=1, `a1=0, a2=1, a3=0` as follows:
242+
store buffers, it is possible to arrive at the final outcome `a0=1, a1=0, a2=1, a3=0` as follows:
243243

244244
[[litms_sb_forward]]
245245
.A store buffer forwarding litmus test (outcome permitted)
@@ -295,7 +295,7 @@ Call this "Rule X". Then we get the following:
295295
preceded (d), then (d) would be required to return the value 1. (This is
296296
a perfectly legal execution; it's just not the one in question)
297297
* (e) precedes (f): by rule X
298-
* (f) precedes (h): by rule <<overlapping-ordering, 4]>>
298+
* (f) precedes (h): by rule <<overlapping-ordering, 4>>
299299
* (h) precedes (a): by the load value axiom, as above.
300300

301301
The global memory order must be a total order and cannot be cyclic,

0 commit comments

Comments
 (0)