Home/Instructions/AES32 Encrypt SubBytes
AES32ESI

RISC-V AES32ESI Instruction Details

Instruction ManualR-type (OP with bs in bits 31:30)

AES final-round encrypt byte step: select a byte from rs2 by bs, apply SubBytes, XOR with rs1

Instruction Syntax

aes32esi rd, rs1, rs2, bs
Operand Breakdown
This is a R-type (OP with bs in bits 31:30)-format instruction. Confirm operand positions based on the assembly syntax.
ZkneCrypto & Security

Instruction Behavior

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.

AES32ESI Decode And Execute Animation

Bounded teaching inputs follow the local official ISA formulas; this does not model a complete AES round, round-key XOR, or microarchitecture.

aes32esi
Execution Context

XLEN is fixed at 32; this animation rejects RV64-sized values.

byte select
fixed
source state
source state
fixed
destination
OP
31..30
bs=01
29..25
10001
24..20
rs2=x12
19..15
rs1=x11
14..12
000
11..7
rd=x10
6..0
0110011
Execution Data Path
rs1[31:0]
0x11223344
rs2[31:0]
0xA1B2C3D4
si
0xC3
aes_sbox_fwd(si)
0x2E
rol32(contribution, shamt)
0x00002E00
Current Step

Decode AES32 OP fields and bs

bits 31..30 are bs, bits 29..25 are 10001; funct3=000 and OP=0110011. This encoding is RV32-only.

encoding: 0x62C58533
syntax: aes32esi a0(x10), a1(x11), a2(x12), 1
Architectural Result
a0(x10) = 0x11221D44

This animation shows only official ISA fields and architectural state, not a particular CPU pipeline, cache, or timing implementation.

Quick Understanding & Search Notes

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.

It selects one byte from rs2 using bs, applies the forward AES S-box, then XORs with rs1; it does not include MixColumns.
Scalar crypto instructions use integer X registers, and the official spec requires the relevant crypto instructions to be implemented with data-independent execution latency.
bs selects a byte from rs2[31:0], and the 32-bit result is sign-extended into rd.

Common Usage Scenarios

Crypto & Security

Understand this scenario with real code like «aes32esi a0, a1, a2, 0».

Data Protection

Understand this scenario with real code like «aes32esi a0, a1, a2, 0».

Pre-Use Checklist

Syntax Check
  • Confirm the current instruction format is R-type (OP with bs in bits 31:30).
  • Confirm the operand order matches the example.
Semantic Check
  • Ensure the destination register usage is compatible with the calling convention.
  • Confirm this is not the lower-level form of a pseudo-instruction expansion.

Pitfalls / Common Confusions

bs selects the byte index (0-3) in rs2[31:0]; rs1 is the XOR source.
Final round omits MixColumns; middle rounds use aes32esmi.

FAQ

Does AES32ESI use floating-point or vector registers?

No. These scalar crypto extension instructions use integer X registers.

Is AES32ESI a complete algorithm implementation?

No. It performs one architecturally defined AES byte step; software still combines instructions and round keys in algorithm order.