From 232c33170282edb9523b1ee60e968863aac62e13 Mon Sep 17 00:00:00 2001 From: Sean Silva Date: Wed, 23 Mar 2016 00:25:13 +0000 Subject: [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 | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'llvm/docs/CommandGuide/bugpoint.rst') diff --git a/llvm/docs/CommandGuide/bugpoint.rst b/llvm/docs/CommandGuide/bugpoint.rst index f11585d359c..6b56f04c835 100644 --- a/llvm/docs/CommandGuide/bugpoint.rst +++ b/llvm/docs/CommandGuide/bugpoint.rst @@ -151,7 +151,12 @@ OPTIONS **--compile-command** *command* This option defines the command to use with the **--compile-custom** - option to compile the bitcode testcase. This can be useful for + option to compile the bitcode testcase. The command should exit with a + failure exit code if the file is "interesting" and should exit with a + success exit code (i.e. 0) otherwise (this is the same as if it crashed on + "interesting" inputs). + + This can be useful for testing compiler output without running any link or execute stages. To generate a reduced unit test, you may add CHECK directives to the testcase and pass the name of an executable compile-command script in this form: -- cgit v1.2.3