You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rmw : relate the read and write events emitted by matching successful load-reserve store conditional instructions, or atomic rmw instructions.
amo: relate the read and write events emitted by atomic rmw instructions.
The second part of the former sounds equivalent to the later to me.
I am right that this mean amo is a subset of rmw, and anything "extra" in rmw is related to load-reserve store conditional instructions? What is the rational of having this rather than having amo as it is, some relation x: relate the read and write events emitted by matching successful load-reserve store conditional instructions and let rmw = x | amo. Some old aarch64 models seem to be following this idea.
Or is this somehow related to the fact that some RMW instructions are represented a single event while other are split into their read and write parts?
The text was updated successfully, but these errors were encountered:
The documentation defines these realtions as
The second part of the former sounds equivalent to the later to me.
I am right that this mean
amo
is a subset ofrmw
, and anything "extra" inrmw
is related to load-reserve store conditional instructions? What is the rational of having this rather than havingamo
as it is, some relationx: relate the read and write events emitted by matching successful load-reserve store conditional instructions
andlet rmw = x | amo
. Some old aarch64 models seem to be following this idea.Or is this somehow related to the fact that some RMW instructions are represented a single event while other are split into their read and write parts?
The text was updated successfully, but these errors were encountered: