X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FBugpoint.html;h=bf75b5ba44c9960dffefc2154c756b24aab32f00;hb=9e6d1d1f5034347d237941f1bf08fba5c1583cd3;hp=bdfd31379a9416a10870c4911bf974d678b10d0c;hpb=04367bfc20c021c4105abf0c33b86d55f782d1e8;p=oota-llvm.git diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html index bdfd31379a9..bf75b5ba44c 100644 --- a/docs/Bugpoint.html +++ b/docs/Bugpoint.html @@ -211,16 +211,22 @@ non-obvious ways. Here are some hints and tips:

you might try llvm-link -v on the same set of input files. If that also crashes, you may be experiencing a linker bug. -

  • If your program is supposed to crash, bugpoint will be - confused. One way to deal with this is to cause bugpoint to ignore the exit - code from your program, by giving it the -check-exit-code=false - option. -
  • bugpoint is useful for proactively finding bugs in LLVM. Invoking bugpoint with the -find-bugs option will cause the list of specified optimizations to be randomized and applied to the program. This process will repeat until a bug is found or the user kills bugpoint. + +
  • bugpoint does not understand the -O option + that is used to specify optimization level to opt. You + can use e.g.

    + +
    +

    opt -O2 -debug-pass=Arguments foo.bc -disable-output

    +
    + +

    to get a list of passes that are used with -O2 and + then pass this list to bugpoint.

    @@ -231,9 +237,9 @@ non-obvious ways. Here are some hints and tips:


    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
    LLVM Compiler Infrastructure