Does bseti access memory?
No data-memory access occurs. The data operation reads integer registers and writes rd; a result directed to x0 is discarded.
Set single bit by immediate index
rd and rs1 select x0–x31; sources are read before writeback, and x0 writes are discarded.
shamt is a nonnegative bit index: 0–31 on RV32 or 0–63 on RV64; RV32 encodings with shamt[5]=1 are reserved. It is not a signed 12-bit operand.
Requires Zbs 1.0 on RV32/RV64; set the selected bit to 1 and preserve the other rs1 bits; an already-set bit stays 1.
bseti is a Zbs single-bit set instruction. The bit index comes from the immediate field.
Starts with machine-code field decoding, then shows operand reads, instruction-specific execution, and ISA-visible state update.
This example uses fixed initial register values and PC=0x2000; instruction fetch succeeds, with no asynchronous interrupt or extra extension checks. Exception branches stop ordinary commit; post-trap PC and handler state are EEI-dependent.
The machine code is split by the current instruction format; the animation starts from encoding/decode.
This animation shows ISA-visible decode and state changes, not any specific CPU pipeline, cache, prediction, or timing implementation.
bseti is a Zbs single-bit set instruction. The bit index comes from the immediate field.
RV32/RV64 Zbs, x11=0x20: bseti x10, x11, 5 writes x10=0x20 because bit 5 is already 1.
No data-memory access occurs. The data operation reads integer registers and writes rd; a result directed to x0 is discarded.
The immediate encodes the bit position directly, with the legal range determined by XLEN.