[llvm-commits] [llvm] r96527 - /llvm/trunk/docs/AdvancedGetElementPtr.html

[Dan Gohman]

Author: djg
Date: Wed Feb 17 16:50:12 2010
New Revision: 96527

URL: http://llvm.org/viewvc/llvm-project?rev=96527&view=rev
Log:
HTML validation fixes.

Modified:
    llvm/trunk/docs/AdvancedGetElementPtr.html

Modified: llvm/trunk/docs/AdvancedGetElementPtr.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/AdvancedGetElementPtr.html?rev=96527&r1=96526&r2=96527&view=diff

==============================================================================
--- llvm/trunk/docs/AdvancedGetElementPtr.html (original)
+++ llvm/trunk/docs/AdvancedGetElementPtr.html Wed Feb 17 16:50:12 2010
@@ -324,20 +324,18 @@
 <div class="doc_text">
    <p>The design of GEP has the following goals, in rough unofficial
       order of priority:</p>
-   <p>
-     <ol>
-       <li>Support C, C-like languages, and languages which can be
-           conceptually lowered into C (this covers a lot).</li>
-       <li>Support optimizations such as those that are common in
-           C compilers.</li>
-       <li>Provide a consistent method for computing addresses so that
-           address computations don't need to be a part of load and
-           store instructions in the IR.</li>
-       <li>Support non-C-like languages, to the extent that it doesn't
-           interfere with other goals.</li>
-       <li>Minimize target-specific information in the IR.</li>
-     </ol>
-   </p>
+   <ol>
+     <li>Support C, C-like languages, and languages which can be
+         conceptually lowered into C (this covers a lot).</li>
+     <li>Support optimizations such as those that are common in
+         C compilers.</li>
+     <li>Provide a consistent method for computing addresses so that
+         address computations don't need to be a part of load and
+         store instructions in the IR.</li>
+     <li>Support non-C-like languages, to the extent that it doesn't
+         interfere with other goals.</li>
+     <li>Minimize target-specific information in the IR.</li>
+   </ol>
 </div>
 
 <!-- *********************************************************************** -->