[LLVMdev] Associate IR instruction with corresponding assembly

Eric Christopher echristo at gmail.com
Mon May 19 08:24:50 PDT 2014


Interesting. My guess is that the debug-ir pass wasn't updated when we
changed some version of the debug metadata and so isn't producing good
metadata.

I'm not sure when I'll get to updating it though and it looks like
Daniel's address is bouncing.

-eric

On Mon, May 19, 2014 at 8:22 AM, shruti padmanabha <shrupad at umich.edu> wrote:
> No. They're both from the 3.4 version of llvm.
> Thanks,
> Shruti
>
>
> On Mon, May 19, 2014 at 11:01 AM, Eric Christopher <echristo at gmail.com>
> wrote:
>>
>> On Sun, May 18, 2014 at 10:28 PM, Tobias Grosser <tobias at grosser.es>
>> wrote:
>> > On 19/05/2014 00:54, shruti padmanabha wrote:
>> >>
>> >> Hi,
>> >>
>> >> Thanks for the pointer. I am unfortunately running into llc problems
>> >> with
>> >> this pass.
>> >> I did
>> >> *opt  -debug-ir   hello.bc -o hello.deb.bc*
>> >>
>> >> *llc -march=arm -debug  -O0 hello.deb.bc  -o hello.deb.s*
>> >>
>> >>
>> >> This is aborting with the error: llc:
>> >> llvm-3.4/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1614: void
>> >> llvm::DwarfDebug::beginFunction(const llvm::MachineFunction*):
>> >> Assertion
>> >> `TheCU && "Unable to find compile unit!"' failed.
>> >> I'm assuming this is because llc found some errors in the metadata that
>> >> debug-ir prints out. How do I find and correct this?
>> >
>> >
>> > This is indeed surprising. I have no idea where this is coming from.
>> > Does
>> > this only happen on ARM? Can you attach the debug.bc file? Or even
>> > better,
>> > open a bug report for that?
>> >
>> > I included Daniel who committed the -debug-ir pass as well as Eric who
>> > has
>> > better knowledge about debug info than me.
>> >
>>
>> Are you mixing versions of llc and opt? I.e. are they both built from
>> the same version?
>>
>> -eric
>
>



More information about the llvm-dev mailing list