Retidy, removing align=left from headings and empty paragraphs

This commit is contained in:
James Gregory 2013-12-30 15:37:13 +11:00
commit a96a114403
362 changed files with 8472 additions and 5040 deletions

View file

@ -1,5 +1,4 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
@ -19,17 +18,21 @@
<center>
<table border="1">
<tr>
<td><a href="01-05.html">Previous</a></td>
<td>
<a href="01-05.html">Previous</a>
</td>
<td><a href="index.html">Table of Contents</a></td>
<td>
<a href="index.html">Table of Contents</a>
</td>
<td><a href="02-01.html">Next</a></td>
<td>
<a href="02-01.html">Next</a>
</td>
</tr>
</table>
</center>
<p><br /></p>
<p><b>LISTING 1.7 L1-7.ASM</b></p>
<pre>
; Assembler subroutine to perform a 16-bit checksum on a block of
@ -103,22 +106,26 @@ _ChecksumChunkendp
<p>Optimization only matters after you&rsquo;ve done your part on the program design end. Consider the ratios on the vertical axis of Table 1.1, which show that optimization is almost totally wasted in the checksumming application without an efficient design. Optimization is no panacea. Table 1.1 shows a two-times improvement from optimization&mdash;and a 50-times-plus improvement from redesign. The longstanding debate about which C compiler optimizes code best doesn&rsquo;t matter quite so much in light of Table 1.1, does it? Your organic optimizer matters much more than your compiler&rsquo;s optimizer, and there&rsquo;s always assembly for those usually small sections of code where performance really matters.</p>
<h4 align="left" id="Heading14">Where We&rsquo;re Going</h4>
<h4 id="Heading14">Where We&rsquo;re Going</h4>
<p>This chapter has presented a quick step-by-step overview of the design process. I&rsquo;m not claiming that this is the only way to create high-performance code; it&rsquo;s just an approach that works for me. Create code however you want, but never forget that design matters more than detailed optimization. Never stop looking for inventive ways to boost performance&mdash;and never waste time speeding up code that doesn&rsquo;t need to be sped up.</p>
<p>I&rsquo;m going to focus on specific ways to create high-performance code from now on. In Chapter 5, we&rsquo;ll continue to look at restartable blocks and internal buffering, in the form of a program that searches files for text strings.</p>
<p><br /></p>
<center>
<table border="1">
<tr>
<td><a href="01-05.html">Previous</a></td>
<td>
<a href="01-05.html">Previous</a>
</td>
<td><a href="index.html">Table of Contents</a></td>
<td>
<a href="index.html">Table of Contents</a>
</td>
<td><a href="02-01.html">Next</a></td>
<td>
<a href="02-01.html">Next</a>
</td>
</tr>
</table>
</center>