Convert figure images to markdown
This commit is contained in:
parent
307b59584f
commit
77a95ec319
115 changed files with 218 additions and 403 deletions
9
11-08.md
9
11-08.md
|
|
@ -33,8 +33,7 @@ have occurred had we executed **POPF**—WITH the bonus that no interrupts
|
|||
can accidentally occur when the Interrupt flag is 0 both before and
|
||||
after the pop.
|
||||
|
||||
\
|
||||
**Figure 11.4** *The operation of POPF.*
|
||||

|
||||
|
||||
How can we push the segment:offset of the next instruction? Well,
|
||||
finding the offset of the next instruction by performing a near call to
|
||||
|
|
@ -61,8 +60,7 @@ with. The code works out like this:
|
|||
; was reached has been popped into the FLAGS register, just as
|
||||
; if a POPF instruction had been executed.
|
||||
|
||||
\
|
||||
**Figure 11.5** *The operation of IRET.*
|
||||

|
||||
|
||||
The operation of this code is illustrated in Figure 11.6.
|
||||
|
||||
|
|
@ -106,8 +104,7 @@ an 8088.)
|
|||
iret
|
||||
endm
|
||||
|
||||
\
|
||||
**Figure 11.6** *Workaround code for the POPF bug.*
|
||||

|
||||
|
||||
The standard version of **EMULATE\_POPF** is 6 bytes longer than
|
||||
**POPF** and much slower, as you'd expect given that it involves three
|
||||
|
|
|
|||
Loading…
Reference in a new issue