<div dir="ltr">This was PR18871 btw.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 18, 2014 at 6:56 PM, Sean Silva <span dir="ltr"><<a href="mailto:silvas@purdue.edu" target="_blank">silvas@purdue.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Author: silvas<br>
Date: Tue Feb 18 17:56:43 2014<br>
New Revision: 201616<br>
<br>
URL: <a href="http://llvm.org/viewvc/llvm-project?rev=201616&view=rev" target="_blank">http://llvm.org/viewvc/llvm-project?rev=201616&view=rev</a><br>
Log:<br>
[docs] Nuke some references to llvm-gcc<br>
<br>
>From a cursory look it seems like all the described commandline options<br>
and such apply to clang just fine, but I'd appreciate a second opinion.<br>
<br>
Modified:<br>
llvm/trunk/docs/HowToSubmitABug.rst<br>
<br>
Modified: llvm/trunk/docs/HowToSubmitABug.rst<br>
URL: <a href="http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/HowToSubmitABug.rst?rev=201616&r1=201615&r2=201616&view=diff" target="_blank">http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/HowToSubmitABug.rst?rev=201616&r1=201615&r2=201616&view=diff</a><br>
==============================================================================<br>
--- llvm/trunk/docs/HowToSubmitABug.rst (original)<br>
+++ llvm/trunk/docs/HowToSubmitABug.rst Tue Feb 18 17:56:43 2014<br>
@@ -43,15 +43,15 @@ the LLVM libraries (e.g. the optimizer o<br>
problems.<br>
<br>
To figure out which component is crashing (the front-end, optimizer or code<br>
-generator), run the ``llvm-gcc`` command line as you were when the crash<br>
+generator), run the ``clang`` command line as you were when the crash<br>
occurred, but with the following extra command line options:<br>
<br>
-* ``-O0 -emit-llvm``: If ``llvm-gcc`` still crashes when passed these<br>
+* ``-O0 -emit-llvm``: If ``clang`` still crashes when passed these<br>
options (which disable the optimizer and code generator), then the crash<br>
is in the front-end. Jump ahead to the section on :ref:`front-end bugs<br>
<front-end>`.<br>
<br>
-* ``-emit-llvm``: If ``llvm-gcc`` crashes with this option (which disables<br>
+* ``-emit-llvm``: If ``clang`` crashes with this option (which disables<br>
the code generator), you found an optimizer bug. Jump ahead to<br>
`compile-time optimization bugs`_.<br>
<br>
@@ -64,12 +64,12 @@ occurred, but with the following extra c<br>
Front-end bugs<br>
--------------<br>
<br>
-If the problem is in the front-end, you should re-run the same ``llvm-gcc``<br>
+If the problem is in the front-end, you should re-run the same ``clang``<br>
command that resulted in the crash, but add the ``-save-temps`` option.<br>
The compiler will crash again, but it will leave behind a ``foo.i`` file<br>
(containing preprocessed C source code) and possibly ``foo.s`` for each<br>
compiled ``foo.c`` file. Send us the ``foo.i`` file, along with the options<br>
-you passed to ``llvm-gcc``, and a brief description of the error it caused.<br>
+you passed to ``clang``, and a brief description of the error it caused.<br>
<br>
The `delta <<a href="http://delta.tigris.org/" target="_blank">http://delta.tigris.org/</a>>`_ tool helps to reduce the<br>
preprocessed file down to the smallest amount of code that still replicates<br>
@@ -92,7 +92,7 @@ Then run:<br>
opt -std-compile-opts -debug-pass=Arguments foo.bc -disable-output<br>
<br>
This command should do two things: it should print out a list of passes, and<br>
-then it should crash in the same way as llvm-gcc. If it doesn't crash, please<br>
+then it should crash in the same way as clang. If it doesn't crash, please<br>
follow the instructions for a `front-end bug`_.<br>
<br>
If this does crash, then you should be able to debug this with the following<br>
@@ -111,9 +111,9 @@ submit the "foo.bc" file and the list of<br>
Code generator bugs<br>
-------------------<br>
<br>
-If you find a bug that crashes llvm-gcc in the code generator, compile your<br>
+If you find a bug that crashes clang in the code generator, compile your<br>
source file to a .bc file by passing "``-emit-llvm -c -o foo.bc``" to<br>
-llvm-gcc (in addition to the options you already pass). Once your have<br>
+clang (in addition to the options you already pass). Once your have<br>
foo.bc, one of the following commands should fail:<br>
<br>
#. ``llc foo.bc``<br>
@@ -138,7 +138,7 @@ the "foo.bc" file and the option that ll<br>
Miscompilations<br>
===============<br>
<br>
-If llvm-gcc successfully produces an executable, but that executable<br>
+If clang successfully produces an executable, but that executable<br>
doesn't run right, this is either a bug in the code or a bug in the<br>
compiler. The first thing to check is to make sure it is not using<br>
undefined behavior (e.g. reading a variable before it is defined). In<br>
<br>
<br>
_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@cs.uiuc.edu">llvm-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a><br>
</blockquote></div><br></div>