search for: debugdwarf

Hi, I run into a a strange error when compiling with debug infos, where LLC tries to generate a variable DIE using a completely wrong frame-index (DebugDwarf tries to resolve frame index 27 in a simple function which only has a single frame object .. ). After digging around, I found that MachineModuleInfo has a VariableDbgInfo map, that is filled by SelectionDAGBuilder. MMI->VariableDbgInfo maps MDNodes representing variables to a <FrameIndex,...

...the verifier, just the reduced test case. Thanks, Nadav On Sep 29, 2013, at 1:40 PM, Stefan Hepp <stefan at stefant.org> wrote: > Hi, > > I run into a a strange error when compiling with debug infos, where LLC tries to generate a variable DIE using a completely wrong frame-index (DebugDwarf tries to resolve frame index 27 in a simple function which only has a single frame object .. ). > > After digging around, I found that MachineModuleInfo has a VariableDbgInfo map, that is filled by SelectionDAGBuilder. > MMI->VariableDbgInfo maps MDNodes representing variables to a &lt...

...an asserts in bool AsmPrinter::doInitialization(Module &M). On the first line: MMI = getAnalysisIfAvailable<MachineModuleInfo>(); This asserts if you use the AsmPrinter the way the DwarfLinker and the AsmPrinter based DwarfGen does if you call this. You must call this to generate the DebugDwarf. If you get past this by installing a Pass then we assert at: GCModuleInfo *MI = getAnalysisIfAvailable<GCModuleInfo>(); assert(MI && "AsmPrinter didn't require GCModuleInfo?"); If we don't have this, we don't get a DwarfDebug. > > Even if we end up...

...le &M). On the first line: >> >> MMI = getAnalysisIfAvailable<MachineModuleInfo>(); >> >> This asserts if you use the AsmPrinter the way the DwarfLinker and the >> AsmPrinter based DwarfGen does if you call this. You must call this to >> generate the DebugDwarf. If you get past this by installing a Pass then we >> assert at: >> >> GCModuleInfo *MI = getAnalysisIfAvailable<GCModuleInfo>(); >> assert(MI && "AsmPrinter didn't require GCModuleInfo?"); >> >> If we don't have this, we don...

...e: > >> > >> MMI = getAnalysisIfAvailable<MachineModuleInfo>(); > >> > >> This asserts if you use the AsmPrinter the way the DwarfLinker and the > >> AsmPrinter based DwarfGen does if you call this. You must call this to > >> generate the DebugDwarf. If you get past this by installing a Pass then > we > >> assert at: > >> > >> GCModuleInfo *MI = getAnalysisIfAvailable<GCModuleInfo>(); > >> assert(MI && "AsmPrinter didn't require GCModuleInfo?"); > >> > >> If...

I have recently been modifying the DWARF parser and have more patches planned and I want to be able to add unit tests that test the internal llvm DWARF APIs to ensure they continue to work and also validate the changes that I am making. There are not many DWARF unit tests other than very simple ones that test DWARF forms currently. I would like to expand this to include many more tests. I had