X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FHowToSubmitABug.html;h=93e0d2107f0d33a4a4997b5a5194b9bfb96b1311;hb=26825a84e97790adaffc55c6101b9fe2524fe1b7;hp=b170aa1e85c88442a07bd6a8c7a583a80014e2e9;hpb=1a5ed97f35a149bcaaefb3b436cdaf9627b55a8b;p=oota-llvm.git diff --git a/docs/HowToSubmitABug.html b/docs/HowToSubmitABug.html index b170aa1e85c..93e0d2107f0 100644 --- a/docs/HowToSubmitABug.html +++ b/docs/HowToSubmitABug.html @@ -67,7 +67,7 @@ information:

@@ -186,6 +186,9 @@ foo.bc, one of the following commands should fail:

  • llc foo.bc -f
  • llc foo.bc -f -relocation-model=pic
  • llc foo.bc -f -relocation-model=static
  • +
  • llc foo.bc -f -enable-eh
  • +
  • llc foo.bc -f -relocation-model=pic -enable-eh
  • +
  • llc foo.bc -f -relocation-model=static -enable-eh
  • If none of these crash, please follow the instructions for a @@ -194,11 +197,16 @@ be able to reduce this with one of the following bugpoint command lines (use the one corresponding to the command above that failed):

      -
    1. bugpoint -run-llc foo.bc --tool-args
    2. +
    3. bugpoint -run-llc foo.bc
    4. bugpoint -run-llc foo.bc --tool-args -relocation-model=pic
    5. bugpoint -run-llc foo.bc --tool-args -relocation-model=static
    6. +
    7. bugpoint -run-llc foo.bc --tool-args -enable-eh
    8. +
    9. bugpoint -run-llc foo.bc --tool-args + -relocation-model=pic -enable-eh
    10. +
    11. bugpoint -run-llc foo.bc --tool-args + -relocation-model=static -enable-eh

    Please run this, then file a bug with the instructions and reduced .bc file @@ -234,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.

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

    -bugpoint -run-jit -output=[correct output file] [bytecode file]  \
    +bugpoint -run-jit -output=[correct output file] [bitcode file]  \
              --tool-args -- [arguments to pass to lli]               \
              --args -- [program arguments]
     
    @@ -270,7 +278,7 @@ bugpoint -run-jit -output=[correct output file] [bytecode file] \
    -bugpoint -run-llc -output=[correct output file] [bytecode file]  \
    +bugpoint -run-llc -output=[correct output file] [bitcode file]  \
              --tool-args -- [arguments to pass to llc]               \
              --args -- [program arguments]
     
    @@ -289,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.

    @@ -298,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:

      @@ -307,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:

      @@ -319,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]