Lines Matching refs:code

13 by optimizers, or bad native code generation (including problems in the static
19 For detailed case scenarios, such as debugging ``opt``, or one of the LLVM code
26 the LLVM infrastructure at all.  It works with any and all LLVM passes and code
45 test program with the "safe" backend (which is assumed to generate good code) to
47 test program, it tries executing it with the selected code generator.  If the
48 selected code generator crashes, ``bugpoint`` starts the `crash debugger`_ on
49 the code generator.  Otherwise, if the resulting output differs from the
50 reference output, it assumes the difference resulted from a code generator
51 failure, and starts the `code generator debugger`_.
53 Finally, if the output of the selected code generator matches the reference
65 If an optimizer or code generator crashes, ``bugpoint`` will try as hard as it
86 The code generator debugger attempts to narrow down the amount of code that is
87 being miscompiled by the selected code generator.  To do this, it takes the test
91 amount of code pushed through the LLVM code generator, to reduce the potential
93 "test" [to be compiled with the code generator] and "safe" [to be compiled with
95 problem.  The code generator debugger assumes that the "safe" backend produces
96 good code.
103 The miscompilation debugger works similarly to the code generator debugger.  It
109 the selected code generator is working properly.
117 * In the code generator and miscompilation debuggers, ``bugpoint`` only works
130 * In the code generator and miscompilation debuggers, debugging will go faster
143   .. code-block:: console
169 TargetLowering both have visitor structured code with lots of potential
171 much code to figure out and the problem seems to be in instcombine, the
182 be helpful.  In this approach, you can modify the source code of instcombine to
194 instcombine are firing.  This can guide where to put additional reporting code.
197 inserting code to limit whether or not to execute the body of the code in the
199 every invocation of the function.  Then add code which simply returns false on
202 .. code-block:: c++
225 code corresponds to the transformation being performed isn't obvious, set a
226 breakpoint after the call count based disabling and step through the code.