search for: thecu

...avoid header pollution, since it's > only on one enum... ;) > > cheers, > --renato > A couple of other questions about DIBuilder: 1) I notice that there's no 'isMain' parameter to CreateCompileUnit. How do you specify the main module? 2) There's no means to set TheCU other than creating a new compile unit. This means that you have to generate all of the debug info for your module with a single DIBuilder instance, since there's no way to use a pre-existing compile unit. -- -- Talin -------------- next part -------------- An HTML attachment was scrubbed......

We have a test case where we are hitting an assertion in the X86 code generator. The assertion is: "Assertion failed: TheCU && "Unable to find compile unit!", file .\..\..\..\lib\CodeGen\AsmPrinter\DwarfDebug.cpp, line 1411" The bitcode is attached. What I am trying to figure out is what is malformed about our debug that is causing this error? This is reproducible with 'llc -march=x86 bugpoi...

Thanks for the quick response. I wrote some code to search “llvm.dbg.cu” for the function (right before the failed assertion): if (TheCU == nullptr) { errs() << "compile unit: " << TheCU << "\n scopeNode(" << FnScope->getScopeNode() << ") => " << *FnScope->getScopeNode() << "\n"; auto fn = MF->getFunction(); errs() << &qu...

On Feb 18, 2011, at 8:31 PM, Talin wrote: > 2) There's no means to set TheCU other than creating a new compile unit. This means that you have to generate all of the debug info for your module with a single DIBuilder instance, since there's no way to use a pre-existing compile unit. TheCU is an internal debug info information that FE should not care about. DIBuilder is...

...mail.com> wrote: > On Tue, Dec 3, 2013 at 10:07 PM, Brandon Holt <bholt at cs.washington.edu> wrote: >> Thanks for the quick response. >> >> I wrote some code to search “llvm.dbg.cu” for the function (right before the >> failed assertion): >> >> if (TheCU == nullptr) { >> errs() << "compile unit: " << TheCU << "\n scopeNode(" << >> FnScope->getScopeNode() << ") => " << *FnScope->getScopeNode() << "\n"; >> auto fn = MF->getFunction...

...ems 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? Thanks again, Shruti On Sat, May 17, 2014 at 5:57 PM, Tobias Grosser <tobias at grosser.es> wr...

On Tue, Dec 3, 2013 at 10:07 PM, Brandon Holt <bholt at cs.washington.edu> wrote: > Thanks for the quick response. > > I wrote some code to search “llvm.dbg.cu” for the function (right before the > failed assertion): > > if (TheCU == nullptr) { > errs() << "compile unit: " << TheCU << "\n scopeNode(" << > FnScope->getScopeNode() << ") => " << *FnScope->getScopeNode() << "\n"; > auto fn = MF->getFunction(); >...

...On Tue, Dec 3, 2013 at 10:07 PM, Brandon Holt <bholt at cs.washington.edu> wrote: >>> Thanks for the quick response. >>> >>> I wrote some code to search “llvm.dbg.cu” for the function (right before the >>> failed assertion): >>> >>> if (TheCU == nullptr) { >>> errs() << "compile unit: " << TheCU << "\n scopeNode(" << >>> FnScope->getScopeNode() << ") => " << *FnScope->getScopeNode() << "\n"; >>> auto fn = MF->g...

...inter errors in this piece of code in DwarfDebug::constructInlinedScopeDIE(): *if* (!Scope->getScopeNode()) *return* NULL; DIScope DS(Scope->getScopeNode()); DIE *ScopeDIE = *new* DIE(dwarf::DW_TAG_inlined_subroutine); DISubprogram InlinedSP = getDISubprogram(DS); CompileUnit *TheCU = getCompileUnit(InlinedSP); DIE *OriginDIE = TheCU->getDIE(InlinedSP); assert(OriginDIE && *"Unable to find Origin DIE!"*); addDIEEntry(ScopeDIE, dwarf::DW_AT_abstract_origin, *dwarf*::DW_FORM_ref4, OriginDIE); What's happening is that InlinedSP.DbgNod...

...eral functions, replacing them with new copies with different types, etc. The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent build of LLVM/Clang from Git mirror): > Assertion failed: (TheCU && "Unable to find compile unit!"), function beginFunction, file ../lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1617. > 0 clang-3.4 0x0000000103ff3808 llvm::sys::PrintStackTrace(__sFILE*) + 40 > 1 clang-3.4 0x0000000103ff3c64 SignalHandler(int...

...>> >> *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. Doe...

...eplacing them with new copies with different types, etc. > > The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent build of LLVM/Clang from Git mirror): > >> Assertion failed: (TheCU && "Unable to find compile unit!"), function beginFunction, file ../lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1617. >> 0 clang-3.4 0x0000000103ff3808 llvm::sys::PrintStackTrace(__sFILE*) + 40 >> 1 clang-3.4 0x0000000103ff3c64 SignalHan...

...>> >> *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....

So, I just sync'd to LLVM tip and added the call to DIBuilder::finalize(). But even with that change I am getting an error when I try to run llc: Assertion failed: (TheCU && "Unable to find compile unit!"), function endFunction, file /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. And looking at the .bc dissassembly, I see there are indeed compile unit MDNodes, although at this level I can't tell if they are hooked...

....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....

...LLVM 2.9 debug version and I'm moving to LLVM 3.2 debug version of metadata. On my example I got llc 3.2 to fail on following assertion: llc: /work1/tools/llvm/3.2/sources/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1471: void llvm::DwarfDebug::endFunction(const llvm::MachineFunction*): Assertion `TheCU && "Unable to find compile unit!"' failed. 0 llc 0x0000000000ffb43f 1 llc 0x0000000000ffd6ba 2 libpthread.so.0 0x00007f5dd70238f0 3 libc.so.6 0x00007f5dd6312a75 gsignal + 53 4 libc.so.6 0x00007f5dd63165c0 abort + 384 5 libc.so.6...

...// FIXME - extra padding for gdb bug. Asm->OutStreamer.AddComment("4 extra padding bytes for GDB"); Asm->EmitInt8(0); Asm->EmitInt8(0); Asm->EmitInt8(0); Asm->EmitInt8(0); Asm->OutStreamer.EmitLabel(Asm->GetTempSymbol("info_end", TheCU->getID())); Does anybody know what the bug is in GDB that this works around? The workaround was added as part of r103439[1], which added support for multiple compilation units in one module. Does the bug ever affect modules with only a single compilation unit? -Ken [1] http://lists.cs.uiuc.ed...

...di.createBasicType   //long >> >> same, you don't need CU here. > > If I don't have a di.createCompileUnit.  di.createFile fails with this message. > > DIBuilder.cpp:59: llvm::DIFile > llvm::DIBuilder::createFile(llvm::StringRef, llvm::StringRef): > Assertion `TheCU && "Unable to create DW_TAG_file_type without > CompileUnit"' failed. > > Which had me scratching my head, If DIFile needs a CU it  would be an > argument to DIBuilder::.createFile > Also type.Verify() thought createBasicType succeeds. I meant type.Verify() fai...

Hi, I am wondering if someone can guide me in adding metadata to IR which already contains some metadata. I am trying to add dbg.declare inst for a local variable I added to a function. I used the DIBuilder to build a DIVariable. When I try to compile llc fails with following message. llc: MCAsmStreamer.cpp:273: virtual void<unnamed>::MCAsmStreamer::EmitLabel(llvm::MCSymbol*): Assertion

On Tue, Nov 9, 2010 at 9:04 AM, Devang Patel <dpatel at apple.com> wrote: > > > On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote: > > On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel < <dpatel at apple.com> > dpatel at apple.com> wrote: > >> >> On Nov 6, 2010, at 7:35 PM, Talin wrote: >> >> After to speaking to Devang