Can SW.AQRL use offset(rs1)?
No. The official syntax is sw.aqrl rs2, (rs1), with no offset immediate; the address comes directly from rs1.
Zalasr atomic store of 4 bytes with acquire+release-RCsc ordering.
SW.AQRL is a 4-byte ordered atomic store in the Zalasr standalone load-acquire/store-release family. It atomically writes the low 32 bits of x[rs2] to the address in x[rs1]; the syntax has no offset field, and rd is fixed to x0 in the encoding. The address is naturally aligned to the access width by default unless relaxed by the misaligned atomicity granule PMA.
Shows the Zalasr standalone store-release AMO encoding, no-offset address syntax, 32-bit data transfer, and aq/rl ordering annotation.
SW.AQRL writes only the low 32 bits of rs2 to memory; higher rs2 bits are not part of the stored value.
This animation shows ISA-visible Zalasr atomic load/store behavior and aq/rl ordering annotations; it does not model LR/SC reservations, AMO read-modify-write old-value return, caches, buses, or pipeline timing.
SW.AQRL uses rs1 directly as the address and atomically writes the low 32 bits of rs2; aq/rl bits provide ordering annotations and do not change the stored data.
Understand this scenario with real code like «sw.aqrl x5, (x6)».
Understand this scenario with real code like «sw.aqrl x5, (x6)».
No. The official syntax is sw.aqrl rs2, (rs1), with no offset immediate; the address comes directly from rs1.
No. These Zalasr instructions are single ordered atomic load/store operations; the animation does not show reservations or old-value return.
No. aq/rl are ordering annotations; the stored value is still the low 32 bits of rs2.