
Decode an RV32I add instruction field by field
Decode 0x007302B3 into RISC-V ADD fields, reconstruct the instruction word, and distinguish ISA facts from processor timing.
The journal / Ideas in progress
Engineering & everyday learningSoftware, systems, and the things I’m learning along the way. From first principles to AI in production.
Find something to readA little theory. A lot of practice.

Decode 0x007302B3 into RISC-V ADD fields, reconstruct the instruction word, and distinguish ISA facts from processor timing.

Trace eight-bit additions to distinguish unsigned carry from signed overflow, then exhaustively check the sign-bit detection rule.

Calculate propagation through a four-bit ripple-carry adder using explicit hypothetical gate delays, then connect the result to a register timing budget.

Trace LB and LBU on byte 0xE2, verify all extension cases, and connect assembly signedness to parser and language type choices.

Select the newest available producer for each operand, trace two writes to the same register, and distinguish forwarding from waiting for an unavailable result.

Trace LRU and FIFO on three array blocks, compare equal-capacity caches, and see why more ways can still leave conflicts or merge separate sets.

Trace six independent instructions through a declared five-stage pipeline, calculate fill and drain overhead, and distinguish bubbles from global stalls.

Derive a sixteen-bit cache address split, trace conflicting reads, check line-spanning byte intervals and recalculate tag storage and associativity.

Place 0x12345678 at four byte addresses, reconstruct it explicitly, and keep byte order separate from width, alignment and signedness.

Trace MMIO access width, compiler constraints, posted-write delivery and device completion with a fictional executable register model.

Compare polling and interrupt completion times with an executable event budget, then identify overload and hybrid-driver boundaries.

Track real byte values, dirty state, eviction and bypassed writes in four explicit cache policies, then compare complete-interval traffic.