From 634ec56986f5832804ce1fef6ddd66fac6103b8c Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sat, 18 Oct 2003 21:34:15 +0000 Subject: Add bugpoint advice section git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9244 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CommandGuide/bugpoint.html | 31 ++++++++++++++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/CommandGuide/bugpoint.html b/docs/CommandGuide/bugpoint.html index 8d83863d9d..04f45b5724 100644 --- a/docs/CommandGuide/bugpoint.html +++ b/docs/CommandGuide/bugpoint.html @@ -105,6 +105,35 @@ being miscompiled. This module assumes that the selected code generator is working properly.

+ +

Advice for using bugpoint

+ +bugpoint can be a remarkably useful tool, but it sometimes works in +non-obvious ways. Here are some hints and tips:

+ +

    +
  1. In code generator and miscompilation debugging modes, bugpoint only + works with programs that have deterministic output. Thus, if the program + outputs the date, time, or any other "random" data, it should be masked out. + +
  2. In code generator and miscompilation debugging modes, debugging will go + faster if you manually modify the program or its inputs to reduce the + runtime, but still exhibit the problem. + +
  3. bugpoint is extremely useful when working on a new optimization: + it helps track down regressions quickly. To avoid having to relink + bugpoint every time you change your optization however, have + bugpoint dynamically load your optimization with the -load option. + +
  4. bugpoint can generate a lot of output and run for a long period of + time. It is often useful to capture the output of the program to file. For + example:
    + bugpoint ..... |& tee bugpoint.log

    + +

+ +

OPTIONS