Does atomic here mean a memory atomic?
No. In Zicsr, atomic means the CSR read and write are performed by one CSR instruction, not an AMO to a memory address.
Read the old CSR value into rd and clear CSR bits selected by 5-bit uimm; uimm=0 suppresses the CSR write
CSRRCI is the immediate form of CSRRC: it reads the old CSR value, zero-extends it to XLEN for rd, then uses the 5-bit unsigned uimm as a low-bit mask to clear corresponding CSR bits. If uimm=0, it does not write the CSR and causes no CSR write side effects; it still reads the CSR.
Shows the Zicsr CSR read-modify-write flow: decode the SYSTEM encoding, read the CSR, compute write/set/clear semantics, then update rd and the CSR.
The CSR name/address is part of the instruction syntax; the old CSR value and rs1 example value are execution context. The animation gives the example CSR no platform-specific field meaning.
CSRRCI is a Zicsr I-type SYSTEM instruction; the CSR address occupies bits 31..20.
The bit view shows the CSR value computation at the selected XLEN.
This animation shows only Zicsr ISA-visible CSR reads/writes, side-effect suppression, and bit-mask semantics; it does not model concrete CSR field meanings, trap handlers, pipelines, or timing.
CSRRCI uses 1 bits in the 5-bit uimm as a clear mask. With uimm=0 it reads the CSR but does not write it.
Understand this scenario with real code like «csrrci x5, mip, 4 # x5 = old mip; clear bit 2 in mip».
Understand this scenario with real code like «csrrci x5, mip, 4 # x5 = old mip; clear bit 2 in mip».
No. In Zicsr, atomic means the CSR read and write are performed by one CSR instruction, not an AMO to a memory address.
No. rd=x0 suppresses the CSR read only for CSRRW/CSRRWI; rs1=x0 or uimm=0 suppresses the CSR write only for CSRRS/CSRRC and their immediate forms.