search for: dibuilder

On Fri, Feb 18, 2011 at 1:52 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 18 February 2011 21:34, Talin <viridia at gmail.com> wrote: > > Sorry, I meant DIBuilder. > > DIBuilder is the new DIFactory. I've been playing with it this week > and it's much easier and straightforward to use. I'm still having > problems to create arrays, though. > > As far as I remember (from the 2010 meeting), the idea was to replace > and deprecat...

...t 23, 2011, at 12:03 AM, Talin wrote: > > Just a follow up on this - I am still having problems, I never did figure > out a solution. (I've been running with debug off for the last month so that > I could get work done.) > > Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I > even put a debug print statement right after it, so that I could be sure > that the code was being executed. I also insured that it was getting called > before the module was written out, and that no additional debug information > gets added after it has been called. &g...

Hi, First, considering I'm using an IRBuilder and a DIBuilder to build my program, how can I automatically bind the CreateAlloca with my named local variable inside the DIBuilder ? Is it automatic with the Twine name of CreateAlloca ? And/Or should I use DIBuilder::createAutoVariable and how ? Then, I'm wondering how to locate back my local variable in m...

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 `Symbol->isUndefined() && "Cannot define a symbol twice!"' failed. I can't...

...e foo.xx DW_TAG_compile_unit, is present in the .debug_pubtypes section. Why is this in the wrong section?? The question: ========= Does anybody have any idea what it is I am doing wrong? The issue seems to be related to generating the info for a CompileUnit. Currently, I am doing this: dibuilder = new DIBuilder(themodule); dibuilder->createCompileUnit(Lang, StringRef("foo.xx")), /*finename*/ StringRef(".") /*Dir*/, StringRef("XXX") /*Producer*/, false /*isOptimized*/, StringRef(&qu...

Hi everybody. I'm trying to use DIBuilder to emit debug information, but in the generated metadata, it appears that references to the compilation unit are being left null. The llvm.dbg.sp node also fails to get generated. Other than these missing pieces, the metadata looks otherwise correct. I am calling DIBuilder::finalize. When I try to...

On Oct 23, 2011, at 12:03 AM, Talin wrote: > Just a follow up on this - I am still having problems, I never did figure out a solution. (I've been running with debug off for the last month so that I could get work done.) > > Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I even put a debug print statement right after it, so that I could be sure that the code was being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called. > > Yet despite...

Sometime about two months ago, something changed in LLVM that broke my frontend's ability to generate debug info. This was around the time that the requirement to call DIBuilder::finalize() was added (and yes, I am calling it.) Specifically, what I am seeing is an assertion failure in llc because it can't find the compile unit for a subroutine. I took a look at the code in DIBuilder.cpp, and I see that indeed it is setting the compile unit to null for all of the vario...

>>> I am  adding local var to existing IR with debug info. I am not using >>> the Pass infrastructure. >>> >>> void InsertDbg(AllocaInst *i, StringRef varname, Instruction, inserbefore) >>> { >>> >>> DIBuilder di(*module); >>> cu = di.createCU        / * How do I get the MDNode of  already in the >>> IR . Instead of recreating it, using filename and directory I knew out >>> of band */ >> >> DIBuilder.createCompileUnit() does not return anything. >> >>&gt...

Hi, I saw your update regarding "*The DIBuilder interface used by front ends to encode debugging information in the LLVM IR now expects clients to use DIBuilder::finalize() at the end of translation unit to complete debugging information encoding"* Does it mean that in the new version you defer emission of some debug info until the transla...

...do something else, you would need to describe that so we understand what you need. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Vivien Millet via llvm-dev Sent: Saturday, March 31, 2018 7:33 AM To: llvm-dev Subject: [llvm-dev] [Dwarf] Register a local variable in DIBuilder and locate it later with a DwarfContext Hi, First, considering I'm using an IRBuilder and a DIBuilder to build my program, how can I automatically bind the CreateAlloca with my named local variable inside the DIBuilder ? Is it automatic with the Twine name of CreateAlloca ? And/Or should I us...

Hi All, DIFactory interface, part of DebugInfo.h, is used to emit LLVM IR constructs to encode debugging information. We are replacing this interface with new simple interface, DIBuilder. Here is one example that demonstrates differences between two interfaces. To create debug information entries to encode volatile type one would use following call in a language front end, CreateDerivedType(DW_TAG_volatile_type, Context, StringRef(), File, 0 /*line no...

..., 2011, at 12:03 AM, Talin wrote: > >> Just a follow up on this - I am still having problems, I never did figure out a solution. (I've been running with debug off for the last month so that I could get work done.) >> >> Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I even put a debug print statement right after it, so that I could be sure that the code was being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called. >> >> Yet...

Just a follow up on this - I am still having problems, I never did figure out a solution. (I've been running with debug off for the last month so that I could get work done.) Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I even put a debug print statement right after it, so that I could be sure that the code was being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called. Yet despite this, the...

Sorry, I meant DIBuilder. On Fri, Feb 18, 2011 at 1:32 PM, Talin <viridia at gmail.com> wrote: > I didn't know DIFactory existed until you mentioned it just now. > > And if folks are adding brand new classes to LLVM, can we not follow the > naming conventions in the developer guidelines? > > O...

...and what you > need. > > --paulr > > > > *From:* llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] *On Behalf Of *Vivien > Millet via llvm-dev > *Sent:* Saturday, March 31, 2018 7:33 AM > *To:* llvm-dev > *Subject:* [llvm-dev] [Dwarf] Register a local variable in DIBuilder and > locate it later with a DwarfContext > > > > Hi, > > First, considering I'm using an IRBuilder and a DIBuilder to build my > program, how can I automatically bind the CreateAlloca with my named local > variable inside the DIBuilder ? Is it automatic with the Twin...

On 18 February 2011 21:34, Talin <viridia at gmail.com> wrote: > Sorry, I meant DIBuilder. DIBuilder is the new DIFactory. I've been playing with it this week and it's much easier and straightforward to use. I'm still having problems to create arrays, though. As far as I remember (from the 2010 meeting), the idea was to replace and deprecate DIFactory. I'm not saying...

> On 2015-Jun-02, at 11:14, Hui Zhang <wayne.huizhang at gmail.com> wrote: > > Any ideas ？ > > Thanks > > On Tue, Jun 2, 2015 at 12:40 PM, Hui Zhang <wayne.huizhang at gmail.com> wrote: > Hello, > > I'm having this assertion fail when I was using DIBuilder to create the debug information: > > Expected no forward declarations! > !719 > > The assertion condition is: !isa<MDNodeFwdDecl> (MD) > > So My questions are: > 1. What is exactly the MDNodeFwdDecl ? I saw it's in the latest release 3.6.1, but I also found thi...

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

On Sun, Sep 4, 2011 at 11:38 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Talin, > > > 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/DwarfDebu...