projects
/
oota-llvm.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
LegalizeTypes can sometimes have deleted nodes
[oota-llvm.git]
/
docs
/
HowToSubmitABug.html
diff --git
a/docs/HowToSubmitABug.html
b/docs/HowToSubmitABug.html
index 26cb58c09401a2b76c2b179dd961629b24e085bf..93e0d2107f0d33a4a4997b5a5194b9bfb96b1311 100644
(file)
--- a/
docs/HowToSubmitABug.html
+++ b/
docs/HowToSubmitABug.html
@@
-67,7
+67,7
@@
information:</p>
<ul>
<li>All information necessary to reproduce the problem.</li>
<li>The reduced test-case that triggers the bug.</li>
<ul>
<li>All information necessary to reproduce the problem.</li>
<li>The reduced test-case that triggers the bug.</li>
- <li>The location where you obtained LLVM (if not from our
CVS
+ <li>The location where you obtained LLVM (if not from our
Subversion
repository).</li>
</ul>
repository).</li>
</ul>
@@
-242,7
+242,7
@@
JIT, or LLC) and optionally a series of LLVM passes to run. For example:</p>
</div>
<p><tt>bugpoint</tt> will try to narrow down your list of passes to the one pass
</div>
<p><tt>bugpoint</tt> will try to narrow down your list of passes to the one pass
-that causes an error, and simplify the b
yte
code file as much as it can to assist
+that causes an error, and simplify the b
it
code file as much as it can to assist
you. It will print a message letting you know how to reproduce the resulting
error.</p>
you. It will print a message letting you know how to reproduce the resulting
error.</p>
@@
-268,7
+268,7
@@
Backend, and then link in the shared object it generates.</p>
<div class="doc_code">
<pre>
<div class="doc_code">
<pre>
-bugpoint -run-jit -output=[correct output file] [b
yte
code file] \
+bugpoint -run-jit -output=[correct output file] [b
it
code file] \
--tool-args -- [arguments to pass to lli] \
--args -- [program arguments]
</pre>
--tool-args -- [arguments to pass to lli] \
--args -- [program arguments]
</pre>
@@
-278,7
+278,7
@@
bugpoint -run-jit -output=[correct output file] [bytecode file] \
<div class="doc_code">
<pre>
<div class="doc_code">
<pre>
-bugpoint -run-llc -output=[correct output file] [b
yte
code file] \
+bugpoint -run-llc -output=[correct output file] [b
it
code file] \
--tool-args -- [arguments to pass to llc] \
--args -- [program arguments]
</pre>
--tool-args -- [arguments to pass to llc] \
--args -- [program arguments]
</pre>
@@
-297,7
+297,7
@@
make bugpoint-jit
</div>
<p>At the end of a successful <tt>bugpoint</tt> run, you will be presented
</div>
<p>At the end of a successful <tt>bugpoint</tt> run, you will be presented
-with two b
yte
code files: a <em>safe</em> file which can be compiled with the C
+with two b
it
code files: a <em>safe</em> file which can be compiled with the C
backend and the <em>test</em> file which either LLC or the JIT
mis-codegenerates, and thus causes the error.</p>
backend and the <em>test</em> file which either LLC or the JIT
mis-codegenerates, and thus causes the error.</p>
@@
-306,7
+306,7
@@
the following:</p>
<ol>
<ol>
-<li><p>Regenerate the shared object from the safe b
yte
code file:</p>
+<li><p>Regenerate the shared object from the safe b
it
code file:</p>
<div class="doc_code">
<p><tt>
<div class="doc_code">
<p><tt>
@@
-315,7
+315,7
@@
the following:</p>
</tt></p>
</div></li>
</tt></p>
</div></li>
-<li><p>If debugging LLC, compile test b
yte
code native and link with the shared
+<li><p>If debugging LLC, compile test b
it
code native and link with the shared
object:</p>
<div class="doc_code">
object:</p>
<div class="doc_code">
@@
-327,7
+327,7
@@
the following:</p>
</div></li>
<li><p>If debugging the JIT, load the shared object and supply the test
</div></li>
<li><p>If debugging the JIT, load the shared object and supply the test
- b
yte
code:</p>
+ b
it
code:</p>
<div class="doc_code">
<p><tt><b>lli</b> -load=safe.so test.bc [program options]</tt></p>
<div class="doc_code">
<p><tt><b>lli</b> -load=safe.so test.bc [program options]</tt></p>