2 ms·
Although these registers are normally not accessible by the programmer, some undocumented instructions provide access to these registers, as will be described l
by userbinator 3y ago
Although these registers are normally not accessible by the programmer, some undocumented instructions provide access to these registers, as will be described later.
Reminds me of the MEMPTR on Z80: https://gist.github.com/drhelius/8497817 https://gist.github.com/drhelius/8497817
Also, I'm not sure if you've explored 8f/1-7 yet, since it's not mentioned in the article, but I suspect it's just the same as pop r/m16 (8f/0) as it ignores the subopcode bits completely. It's very weird that the push and pop are in completely different places in the opcode map.
- toast0 3y ago> It's very weird that the push and pop are in completely different places in the opcode map. Are they? There's a lot of different opcodes for push and pop, but if I'm reading right, for a given address mode, the op code for push and pop always differs by one bit (which bit changes though) https://www.felixcloutier.com/x86/push https://www.felixcloutier.com/x86/push https://www.felixcloutier.com/x86/pop https://www.felixcloutier.com/x86/pop
- kens 3y agoI hadn't noticed that characteristic of 8F. Looking at the microcode, the subopcode bits are ignored, so I think your analysis is correct. I agree that it's very weird that PUSH rm and POP rm are arranged completely differently. The obvious place to put POP would be in FF/7, especially since that spot is unused. I can't think of any reason why they wouldn't do that.
- peterfirefly 3y ago> Looking at the microcode, the subopcode bits are ignored, so I think your analysis is correct. That's what Andrew Jenner's emulator code does. https://github.com/reenigne/reenigne/blob/master/8088/xtce/xtce.h https://github.com/reenigne/reenigne/blob/master/8088/xtce/x... Line 3049.
- rep_lodsb 3y agoThe reason is that opcode FE/FF with a memory operand will always read it into the 'M' register, which would be unwanted for POP.