projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 49a59ca) | patch
[docs] Clarify the sense of --compile-command
authorSean Silva <chisophugis@gmail.com>
Wed, 23 Mar 2016 00:25:13 +0000 (00:25 +0000)
committerSean Silva <chisophugis@gmail.com>
Wed, 23 Mar 2016 00:25:13 +0000 (00:25 +0000)
commit232c33170282edb9523b1ee60e968863aac62e13
treec97c62e3f0a92fa96f7cd69a8d70bf5ddba70c53tree | snapshot
parent49a59ca0930f3038e5bfc8cea66f06be957ecf92commit | diff
[docs] Clarify the sense of --compile-command

In retrospect, it seems "obvious" that the sense of the return code is
the same as if it crashed on "interesting" inputs. But that didn't stop
me from spending more time than I care to admit verifying this.

llvm-svn: 264119
llvm/docs/CommandGuide/bugpoint.rst diff | blob | history
Domain: System / Toolchain;