Does AES32ESI use floating-point or vector registers?
No. These scalar crypto extension instructions use integer X registers.
AES final-round encrypt byte step: select a byte from rs2 by bs, apply SubBytes, XOR with rs1
aes32esi is an RV32 scalar AES final-round encrypt instruction in Zkne. It selects a byte from rs2[31:0] using bs, applies the AES forward S-box, rotates the result left into the position selected by bs, XORs it with rs1[31:0], and writes rd; this final-round form does not include MixColumns.
Bounded teaching inputs follow the local official ISA formulas; this does not model a complete AES round, round-key XOR, or microarchitecture.
XLEN is fixed at 32; this animation rejects RV64-sized values.
bits 31..30 are bs, bits 29..25 are 10001; funct3=000 and OP=0110011. This encoding is RV32-only.
This animation shows only official ISA fields and architectural state, not a particular CPU pipeline, cache, or timing implementation.
AES32ESI is a Zkne scalar cryptography instruction for AES final-round encrypt byte step. This page is checked against the official scalar crypto extension, avoiding confusion among round functions, key schedule steps, and operand sources.
Understand this scenario with real code like «aes32esi a0, a1, a2, 0».
Understand this scenario with real code like «aes32esi a0, a1, a2, 0».
No. These scalar crypto extension instructions use integer X registers.
No. It performs one architecturally defined AES byte step; software still combines instructions and round keys in algorithm order.