Use <pre> instead of <p><tt> combo to decrease space used for code blocks.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@13573 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Misha Brukman 2004-05-14 19:04:07 +00:00
parent 1e4ae2b329
commit 3c687a0925

View File

@ -148,8 +148,7 @@ compilation, compile your test-case to a <tt>.s</tt> file with the
<tt>-save-temps</tt> option to <tt><b>llvm-gcc</b></tt>. Then run:</p>
<div class="doc_code">
<p><tt><b>gccas</b> -debug-pass=Arguments &lt; /dev/null -o - &gt; /dev/null
</tt></p>
<pre><b>gccas</b> -debug-pass=Arguments &lt; /dev/null -o - &gt; /dev/null</pre>
</div>
<p>... which will print a list of arguments, indicating the list of passes that
@ -172,8 +171,9 @@ being linked together (the "<tt><b>llvm-gcc</b> -v</tt>" output should include
the full list of objects linked). Then run:</p>
<div class="doc_code">
<p><tt><b>llvm-as</b> &lt; /dev/null &gt; null.bc
<b>gccld</b> -debug-pass=Arguments null.bc</tt></p>
<pre>
<b>llvm-as</b> &lt; /dev/null &gt; null.bc
<b>gccld</b> -debug-pass=Arguments null.bc</tt></p>
</div>
<p>... which will print a list of arguments, indicating the list of passes that
@ -196,7 +196,7 @@ order to reduce the list of passes (which is probably large) and the input to
something tractable, use the <tt><b>bugpoint</b></tt> tool as follows:</p>
<div class="doc_code">
<p><tt><b>bugpoint</b> &lt;input files&gt; &lt;list of passes&gt;</tt></p>
<pre><b>bugpoint</b> &lt;input files&gt; &lt;list of passes&gt;</pre>
</div>
<p><tt><b>bugpoint</b></tt> will print a bunch of output as it reduces the
@ -242,8 +242,8 @@ which code generator you wish to compile the program with (e.g. C backend, the
JIT, or LLC) and optionally a series of LLVM passes to run. For example:</p>
<div class="doc_code">
<p><tt><b>bugpoint</b> -run-cbe [... optimization passes ...] file-to-test.bc
--args -- [program arguments]</tt></p>
<pre>
<b>bugpoint</b> -run-cbe [... optimization passes ...] file-to-test.bc --args -- [program arguments]</pre>
</div>
<p><tt>bugpoint</tt> will try to narrow down your list of passes to the one pass
@ -295,8 +295,10 @@ debug the JIT, LLC, and CBE, using the pre-written Makefile targets, which
will pass the program options specified in the Makefiles:</p>
<div class="doc_code">
<p><tt>cd llvm/test/../../program<br>
make bugpoint-jit</tt></p>
<pre>
cd llvm/test/../../program
make bugpoint-jit
</pre>
</div>
<p>At the end of a successful <tt>bugpoint</tt> run, you will be presented
@ -309,28 +311,32 @@ the following:</p>
<ol>
<li><p>Regenerate the shared object from the safe bytecode file:</p>
<li><p>Regenerate the shared object from the safe bytecode file:</p>
<div class="doc_code">
<p><tt><b>llc</b> -march=c safe.bc -o safe.c<br>
<b>gcc</b> -shared safe.c -o safe.so</tt></p>
</div></li>
<div class="doc_code">
<pre>
<b>llc</b> -march=c safe.bc -o safe.c
<b>gcc</b> -shared safe.c -o safe.so
</pre>
</div></li>
<li><p>If debugging LLC, compile test bytecode native and link with the shared
object:</p>
<li><p>If debugging LLC, compile test bytecode native and link with the shared
object:</p>
<div class="doc_code">
<p><tt><b>llc</b> test.bc -o test.s -f<br>
<b>gcc</b> test.s safe.so -o test.llc<br>
./test.llc [program options]</tt></p>
</div></li>
<li><p>If debugging the JIT, load the shared object and supply the test
bytecode:</p>
<div class="doc_code">
<pre>
<b>llc</b> test.bc -o test.s -f
<b>gcc</b> test.s safe.so -o test.llc
./test.llc [program options]
</pre>
</div></li>
<li><p>If debugging the JIT, load the shared object and supply the test
bytecode:</p>
<div class="doc_code">
<p><tt><b>lli</b> -load=safe.so test.bc [program options]</tt></p>
</div></li>
<div class="doc_code">
<pre><b>lli</b> -load=safe.so test.bc [program options]</pre>
</div></li>
</ol>