6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-08-12 17:25:49 +00:00
Code Issues Projects Releases Wiki Activity

* Remove note about "UNSUPPORTED: " feature that just became supported

Browse Source 
* Fix usage of <p> tag and some grammar


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@13062 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Misha Brukman
2004-04-19 03:28:39 +00:00
parent b687d82b02
commit f6f7ec1ee2
1 changed files with 6 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/CommandGuide/bugpoint.html
View File

@@ -90,22 +90,17 @@ href="analyze.html">analyze</a></tt>, or <tt><a href="llc.html">llc</a></tt>.<p>
<a name="codegendebug"> <a name="codegendebug">
<h4>Code generator debugger</h4> <h4>Code generator debugger</h4>
The code generator debugger attempts to narrow down the amount of code that is <p>The code generator debugger attempts to narrow down the amount of code that
being miscompiled by the <a href="#opt_run-">selected</a> code generator. To do is being miscompiled by the <a href="#opt_run-">selected</a> code generator. To
this, it takes the test program and partitions it into two pieces: one piece do this, it takes the test program and partitions it into two pieces: one piece
which it compiles with the C backend (into a shared object), and one piece which which it compiles with the C backend (into a shared object), and one piece which
it runs with either the JIT or the static LLC compiler. It uses several it runs with either the JIT or the static LLC compiler. It uses several
techniques to reduce the amount of code pushed through the LLVM code generator, techniques to reduce the amount of code pushed through the LLVM code generator,
to reduce the potential scope of the problem. After it is finished, it emits to reduce the potential scope of the problem. After it is finished, it emits
two bytecode files (called "test" [to be compiled with the code generator] and two bytecode files (called "test" [to be compiled with the code generator] and
"safe" [to be compiled with the C backend] respectively), and instructions for "safe" [to be compiled with the C backend], respectively), and instructions for
reproducing the problem. The code generator debugger assumes that the C reproducing the problem. The code generator debugger assumes that the C backend
backend produces good code.<p> produces good code.</p>
If you are using the code generator debugger and get an error message that
says "UNSUPPORTED: external function used as a global initializer!", try using
the <tt>-run-llc</tt> option instead of the <tt>-run-jit</tt> option. This is
due to an unimplemented feature in the code generator debugger.<p>
<a name="miscompilationdebug"> <a name="miscompilationdebug">
<h4>Miscompilation debugger</h4> <h4>Miscompilation debugger</h4>