On Wed, 20 Apr 2005, Markus F.X.J. Oberhumer wrote:> Misha Brukman wrote:
>> On Tue, Apr 19, 2005 at 07:01:40AM +0200, Markus F.X.J. Oberhumer
wrote:
>>
>>> While trying to hunt down a codegen bug (not yet found) ...
>>
>> Have you considered using bugpoint for your codegen debugging needs?
>> http://llvm.cs.uiuc.edu/docs/Bugpoint.html#codegendebug
>
> Well, the (critical) bug in question was
> http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=548 , and I'm not sure if
> bugpoint could have helped me reducing the testcase down from a huge
program.
> But then, I've never looked too closely - is there a small tutorial ?
Misha pointed out this document, which has the basics:
http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html
This document contains more detail:
http://llvm.cs.uiuc.edu/docs/Bugpoint.html
Like Misha said, bugpoint can track down problems in the JIT, in the
native code generators, or in optimization passes. Generally reducing the
"problem" down to an individual function, a loop, a basic block, or
even a
few llvm instructions depending on what is necessary to reproduce the
problem.
For people that are doing llvm optimizer and codegen development, I highly
recommend looking into it. :)
-Chris
--
http://nondot.org/sabre/
http://llvm.cs.uiuc.edu/
