From 721c201bd55ffb73cb2ba8d39e0570fa38c44e15 Mon Sep 17 00:00:00 2001 From: dim Date: Wed, 15 Aug 2012 19:34:23 +0000 Subject: Vendor import of llvm trunk r161861: http://llvm.org/svn/llvm-project/llvm/trunk@161861 --- docs/HowToSubmitABug.html | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) (limited to 'docs/HowToSubmitABug.html') diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html index 0071ec6..ef7cf9e 100644 --- a/docs/HowToSubmitABug.html +++ b/docs/HowToSubmitABug.html @@ -4,7 +4,7 @@ How to submit an LLVM bug report - + @@ -31,9 +31,6 @@ Misha Brukman

- - Debugging - @@ -226,12 +223,12 @@ we have chased down ended up being bugs in the program being compiled, not LLVM.

Once you determine that the program itself is not buggy, you should choose -which code generator you wish to compile the program with (e.g. C backend, the -JIT, or LLC) and optionally a series of LLVM passes to run. For example:

+which code generator you wish to compile the program with (e.g. LLC or the JIT) +and optionally a series of LLVM passes to run. For example:

-bugpoint -run-cbe [... optzn passes ...] file-to-test.bc --args -- [program arguments]

+bugpoint -run-llc [... optzn passes ...] file-to-test.bc --args -- [program arguments]

bugpoint will try to narrow down your list of passes to the one pass @@ -341,7 +338,7 @@ the following:

Chris Lattner
The LLVM Compiler Infrastructure
- Last modified: $Date: 2011-10-31 12:21:59 +0100 (Mon, 31 Oct 2011) $ + Last modified: $Date: 2012-06-14 18:52:55 +0200 (Thu, 14 Jun 2012) $ -- cgit v1.1