Skip to content

Commit

Permalink
More ARC feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
Brendan Sweeney committed Nov 18, 2024
1 parent c7db828 commit 6b20bc8
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 10 deletions.
2 changes: 1 addition & 1 deletion chapter2.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The instructions in the Zalasr extension require that the address held in _rs1_
If the address is not naturally aligned, an address-misaligned exception or an access-fault exception will be generated.
The access-fault exception can be generated for a memory access that would otherwise be able to complete except for the misalignment, if the misaligned access should not be emulated.

The misaligned atomicity granule PMA applies to instructions in the Zalasr extension.
The misaligned atomicity granule PMA, defined in Volume II of this manual, optionally relaxes this alignment requirement.
If all accessed bytes lie within the same misaligned atomicity granule, the instruction will not raise an exception for reasons of address alignment, and the instruction will give rise to only one memory operation for the purposes of RVWMO—i.e., it will execute atomically.


Expand Down
9 changes: 0 additions & 9 deletions intro.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,3 @@ As seen in cite:[hansdoc], these can be important for high performance designs.

They are also widely used in language-level memory models.
Both the Java cite:[manson2005java] and {cpp} cite:[boehm2008foundations] memory models make use of acquire-release semantics, and {cpp}'s `atomic` provides primitives that are meant to map directly to load-acquire and store-release instructions.

== Suitability for inclusion in the fast-track process

This extension is suitable for inclusion in the fast-track process because it is small, self-contained, and uncontroversial.
It adds only two new instructions (although with 8 variants of each of them).
It addresses a pressing need (being able to efficiently map the {cpp} memory model) that has already been considered (notes are already made in the memory model for its addition).
Mailing list discussion has been primarily over details, with the core aspects being uncontroversial.
This proposal is complete, even coming with SAIL code.
Therefore, this extension should be included in the fast-track process.

0 comments on commit 6b20bc8

Please sign in to comment.