X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FHowToSubmitABug.html;h=bdec1c091096f971ea6bbee5a035259cbdeea965;hb=c69485e34d57e17fe2c3acab64e519d6a6945197;hp=26cb58c09401a2b76c2b179dd961629b24e085bf;hpb=c25904f23a361d6550b7a2f5446707a6df31c3fb;p=oota-llvm.git diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html index 26cb58c0940..bdec1c09109 100644 --- a/docs/HowToSubmitABug.html +++ b/docs/HowToSubmitABug.html @@ -67,7 +67,7 @@ information:

@@ -242,7 +242,7 @@ JIT, or LLC) and optionally a series of LLVM passes to run. For example:

bugpoint will try to narrow down your list of passes to the one pass -that causes an error, and simplify the bytecode file as much as it can to assist +that causes an error, and simplify the bitcode file as much as it can to assist you. It will print a message letting you know how to reproduce the resulting error.

@@ -268,8 +268,8 @@ Backend, and then link in the shared object it generates.

-bugpoint -run-jit -output=[correct output file] [bytecode file]  \
-         --tool-args -- [arguments to pass to lli]               \
+bugpoint -run-jit -output=[correct output file] [bitcode file]  \
+         --tool-args -- [arguments to pass to lli]              \
          --args -- [program arguments]
 
@@ -278,8 +278,8 @@ bugpoint -run-jit -output=[correct output file] [bytecode file] \
-bugpoint -run-llc -output=[correct output file] [bytecode file]  \
-         --tool-args -- [arguments to pass to llc]               \
+bugpoint -run-llc -output=[correct output file] [bitcode file]  \
+         --tool-args -- [arguments to pass to llc]              \
          --args -- [program arguments]
 
@@ -297,7 +297,7 @@ make bugpoint-jit

At the end of a successful bugpoint run, you will be presented -with two bytecode files: a safe file which can be compiled with the C +with two bitcode files: a safe file which can be compiled with the C backend and the test file which either LLC or the JIT mis-codegenerates, and thus causes the error.

@@ -306,7 +306,7 @@ the following:

    -
  1. Regenerate the shared object from the safe bytecode file:

    +
  2. Regenerate the shared object from the safe bitcode file:

    @@ -315,7 +315,7 @@ the following:

  3. -
  4. If debugging LLC, compile test bytecode native and link with the shared +

  5. If debugging LLC, compile test bitcode native and link with the shared object:

    @@ -327,7 +327,7 @@ the following:

  6. If debugging the JIT, load the shared object and supply the test - bytecode:

    + bitcode:

    lli -load=safe.so test.bc [program options]

    @@ -341,9 +341,9 @@ the following:


    Valid CSS! + src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"> Valid HTML 4.01! + src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"> Chris Lattner
    The LLVM Compiler Infrastructure