Lines Matching +full:runs +full:- +full:on

30 compiler-debugging process; consequently, it may take a long period of
36 ----------------------------
38 ``bugpoint`` reads each ``.bc`` or ``.ll`` file specified on the command line
40 LLVM passes are specified on the command line, it runs these passes on the test
44 Otherwise, if the ``-output`` option was not specified, ``bugpoint`` runs the
48 selected code generator crashes, ``bugpoint`` starts the `crash debugger`_ on
54 output, ``bugpoint`` runs the test program after all of the LLVM passes have
63 --------------
69 ``opt``, for example, because it runs over 38 passes.
78 bitcode file, and give you instructions on how to reproduce the failure with
84 -----------------------
89 "safe" backend (into a shared object), and one piece which it runs with either
101 -----------------------
105 specified on one piece, linking the two pieces back together, and then executing
115 non-obvious ways.  Here are some hints and tips:
128   message, see ``-compile-command`` in :doc:`CommandGuide/bugpoint`.
134 * ``bugpoint`` is extremely useful when working on a new optimization: it helps
137   your optimization with the ``-load`` option.
143   .. code-block:: console
148   as on your terminal.
151   crashes before you see its "All input ok" message, you might try ``llvm-link
152   -v`` on the same set of input files. If that also crashes, you may be
156   ``bugpoint`` with the ``-find-bugs`` option will cause the list of specified
161   -passes=metarenamer`` over the IR to rename everything using easy-to-read,
162   metasyntactic names. Alternatively, run ``opt -passes=strip,instnamer`` to
175 Turn on ``-debug-only=instcombine`` and see which transformations within
183 disable just those transformations that are being performed on your test input
193 You may also find it useful to use "``-stats``" now to see what parts of
198 visit function can be helpful.  Add a static counter which is incremented on
199 every invocation of the function.  Then add code which simply returns false on
202 .. code-block:: c++
214   LLVM_DEBUG(dbgs() << "I: "; I->dump());
218 point---a simple binary search may not be sufficient, as transformations that