Gregory's ServerThus, a simple add takes 3 micro-instructions (and 3 clock cycles). The microcode is very generic: it doesn't know the particular registers, the ALU operation, or the operand size. It just specifies the steps and the hardware figures out the details. This keeps microcode small.
|
6 comments
 Each of the 8 addressing formulas has a short microcode subroutine to compute the effective address. The 8086's Translation ROM determines the appropriate 13-bit microcode address based on the ModR/M byte. For an addressing mode with a displacement "ADD AX,[SI+1234]", a few more lines of microcode fetch the displacement bytes (e.g. 1234) from the instruction prefetch queue (Q), put them in tmpB, and add them to the SI value. The 8086 chip squeezed a lot of functionality into just 512 words of microcode, making hardware take care of details. The die photo shows these functional blocks on the die. Microcode takes a large area but even registers (like M and N) use a substantial area of the silicon. Microcode is very low level and pretty tricky, but hopefully this brief Mastodon explanation makes some sense. For a more detailed look at microcode, see my blog post: https://www.righto.com/2023/02/8086-modrm-addressing.html Thanks to Andrew Jenner for disassembling the 8086 microcode. |
Adding to memory "ADD [SI],AX" uses the same microcode. A microcode subroutine gets the SI address and reads (R) from memory. Now M represents the memory value. The microcode adds, then falls through to write (W) the result to memory due to the writeback (WB) condition.