Convert notes into blockquotes
This commit is contained in:
parent
832fb15e54
commit
8ed9dea394
105 changed files with 884 additions and 411 deletions
14
12-04.md
14
12-04.md
|
|
@ -75,9 +75,11 @@ presumably, **MOV CL,AL** interrupts the pipeline again because the
|
|||
pipeline is now on its first cycle: the one that loading a byte register
|
||||
can affect.
|
||||
|
||||
------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
 *I know—it seems awfully complicated. It isn't, really. Generally, try not to use byte destinations exactly two cycles before using a register to address memory, and try not to load a register either one or two cycles before using it to address memory, and you'll be fine.*
|
||||
------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
> 
|
||||
> I know—it seems awfully complicated. It isn't, really. Generally, try
|
||||
> not to use byte destinations exactly two cycles before using a register
|
||||
> to address memory, and try not to load a register either one or two
|
||||
> cycles before using it to address memory, and you'll be fine.
|
||||
|
||||
#### Timing Your Own 486 Code {#Heading11}
|
||||
|
||||
|
|
@ -143,9 +145,9 @@ more than doubles to 224 µs, or 3.7 cycles per repetition; the extra
|
|||
seven-tenths of a cycle comes from fetching non-cached instruction
|
||||
bytes.
|
||||
|
||||
------------------- -----------------------------------------------------------------------------------------------------------------------
|
||||
 *Whenever you see non-integral timing results of this sort, it's a good bet that the test code or data isn't cached.*
|
||||
------------------- -----------------------------------------------------------------------------------------------------------------------
|
||||
> 
|
||||
> Whenever you see non-integral timing results of this sort, it's a good
|
||||
> bet that the test code or data isn't cached.
|
||||
|
||||
### The Story Continues {#Heading12}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue