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
37-02.md
6
37-02.md
|
|
@ -26,7 +26,7 @@ profiling before you optimize.
|
|||
|
||||
When I went to speed up run-length slice lines, I initially manually
|
||||
converted the last chapter's C code into assembly. Then I streamlined
|
||||
the register usage and used **REP STOS** wherever possible. Listing 37.1
|
||||
the register usage and used `REP STOS` wherever possible. Listing 37.1
|
||||
is that code. At that point, line drawing was surely faster, although I
|
||||
didn't know exactly how much faster. Equally surely, there were
|
||||
significant optimizations yet to be made, and I was itching to get on to
|
||||
|
|
@ -94,8 +94,8 @@ the freed registers could be used to implement more esoteric approaches
|
|||
like unrolling the Y-major inner loop; such unrolling could take
|
||||
advantage of the knowledge that only two run lengths are possible for
|
||||
any given line. Strangely enough, on the 486 it might also be worth
|
||||
unrolling the X-major inner loop, which consists of **REP STOSB**,
|
||||
because of the slow start-up time of **REP** relative to the speed of
|
||||
unrolling the X-major inner loop, which consists of `REP STOSB`,
|
||||
because of the slow start-up time of `REP` relative to the speed of
|
||||
branching on that processor.
|
||||
|
||||
Special code could be implemented for lines with integral slopes,
|
||||
|
|
|
|||
Loading…
Reference in a new issue