Change bold code snippets to inline code blocks
This commit is contained in:
parent
f658bfbb40
commit
3c76d884ef
185 changed files with 1772 additions and 1772 deletions
6
25-01.md
6
25-01.md
|
|
@ -43,14 +43,14 @@ unmodified, AND, OR, and XOR) that we looked at in the last chapter.
|
|||
The barrel shifter is powerful, but (as sometimes happens in this
|
||||
business) it sounds more useful than it really is. This is because the
|
||||
GC can only rotate CPU data, a task that the CPU itself is perfectly
|
||||
capable of performing. Two **OUT**s are needed to select a given
|
||||
capable of performing. Two `OUT`s are needed to select a given
|
||||
rotation: one to set the GC Index register, and one to set the Data
|
||||
Rotate register. However, with careful programming it's sometimes
|
||||
possible to leave the GC Index always pointing to the Data Rotate
|
||||
register, so only one **OUT** is needed. Even so, it's often easier
|
||||
register, so only one `OUT` is needed. Even so, it's often easier
|
||||
and/or faster to simply have the CPU rotate the data of interest CL
|
||||
times than to set the Data Rotate register. (Bear in mind that a single
|
||||
**OUT** takes from 11 to 31 cycles on a 486—and longer if the VGA is
|
||||
`OUT` takes from 11 to 31 cycles on a 486—and longer if the VGA is
|
||||
sluggish at responding to OUTs, as many VGAs are.) If only the VGA could
|
||||
rotate *latched* data, then there would be all sorts of useful
|
||||
applications for rotation, but, sadly, only CPU data can be rotated.
|
||||
|
|
|
|||
Loading…
Reference in a new issue