aboutsummaryrefslogtreecommitdiffstats
path: root/docs/HowToSubmitABug.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/HowToSubmitABug.html')
-rw-r--r--docs/HowToSubmitABug.html11
1 files changed, 4 insertions, 7 deletions
diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html
index baefce3..39f8385 100644
--- a/docs/HowToSubmitABug.html
+++ b/docs/HowToSubmitABug.html
@@ -4,7 +4,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>How to submit an LLVM bug report</title>
- <link rel="stylesheet" href="llvm.css" type="text/css">
+ <link rel="stylesheet" href="_static/llvm.css" type="text/css">
</head>
<body>
@@ -31,9 +31,6 @@
<a href="http://misha.brukman.net">Misha Brukman</a></p>
</div>
</td>
-<td class="right">
- <img src="img/Debugging.gif" alt="Debugging" width="444" height="314">
-</td>
</tr>
</table>
@@ -226,12 +223,12 @@ we have chased down ended up being bugs in the program being compiled, not
LLVM.</p>
<p>Once you determine that the program itself is not buggy, you should choose
-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>
+which code generator you wish to compile the program with (e.g. LLC or the JIT)
+and optionally a series of LLVM passes to run. For example:</p>
<div class="doc_code">
<p><tt>
-<b>bugpoint</b> -run-cbe [... optzn passes ...] file-to-test.bc --args -- [program arguments]</tt></p>
+<b>bugpoint</b> -run-llc [... optzn passes ...] file-to-test.bc --args -- [program arguments]</tt></p>
</div>
<p><tt>bugpoint</tt> will try to narrow down your list of passes to the one pass