6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-14 11:32:34 +00:00
Code Issues Projects Releases Wiki Activity

Suggest -save-temps instead of -S, -E.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@6318 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Brian Gaeke 2003-05-23 21:03:50 +00:00
parent 6ae73dc98f
commit eefe979c91
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/HowToSubmitABug.html
View File

@ -95,11 +95,14 @@ have at this point.
<a name="front-end">Front-end bugs <a name="front-end">Front-end bugs
</b></font></td></tr></table><ul> </b></font></td></tr></table><ul>
If the problem is in the front-end, pretty much the only thing you can do is If the problem is in the front-end, you should re-run the same
preprocess the input (compile with the <tt>-E</tt> option) and send us the <tt>llvm-gcc</tt> command that resulted in the crash, but add the
results. There is no good way to reduce source-level test-cases that I know <tt>-save-temps</tt> option. The compiler will crash again, but it
of... if you do know, send me information and we can extend this section. :)<p> will leave behind a <tt><i>foo</i>.i</tt> file (containing preprocessed
C source code) and possibly <tt><i>foo</i>.s</tt> (containing LLVM
assembly code), for each compiled <tt><i>foo</i>.c</tt> file. Send us
the <tt><i>foo</i>.i</tt> file, along with a brief description of the
error it caused.<p>
<!-- ======================================================================= --> <!-- ======================================================================= -->
</ul><table width="100%" bgcolor="#441188" border=0 cellpadding=4 cellspacing=0> </ul><table width="100%" bgcolor="#441188" border=0 cellpadding=4 cellspacing=0>
@ -109,8 +112,8 @@ of... if you do know, send me information and we can extend this section. :)<p>
</b></font></td></tr></table><ul> </b></font></td></tr></table><ul>
If you find that a bug crashes in the <tt><b>gccas</b></tt> stage of If you find that a bug crashes in the <tt><b>gccas</b></tt> stage of
compilation, compile your test-case to a <tt>.s</tt> file with the <tt>-S</tt> compilation, compile your test-case to a <tt>.s</tt> file with the
option to <tt><b>llvm-gcc</b></tt>. Then run:<p> <tt>-save-temps</tt> option to <tt><b>llvm-gcc</b></tt>. Then run:<p>
<pre> <pre>
<b>gccas</b> -debug-pass=Arguments &lt; /dev/null -o - &gt; /dev/null <b>gccas</b> -debug-pass=Arguments &lt; /dev/null -o - &gt; /dev/null