similar to: [DebugInfo][DIBuilder] Good way to pass arguments to createClassType/createMemberType

At least for generating DWARF the scope of of a composite type member should be irrelevant since it will always be nested inside its parent. -- adrian > On Feb 6, 2019, at 10:24 AM, David Blaikie <dblaikie at gmail.com> wrote: > > A good rough rule of thumb here is "what would/does Clang do?" & it looks (to me, on a very cursory glance) like Clang mostly passes the

Hello, I'm using DIBuilder to create debugging information, I'm not clear about two things: [1] Could you help explain the meaning and the difference between"alignment" and "offset" of a type ? e.g class Actor{ int age; const char* name; } Besides, I found the denotation of createMemberType and createStructType both have "Member

Hello, Richard Thanks a lot ! On Fri, Dec 19, 2014 at 10:04 AM, RICHARD STUCKEY < richard.stuckey at virgin.net> wrote: > > Hi, Hui Zang, > > It helps to remember that at runtime a variable of a structure type has to > be allocated store, and to think about how that variable is laid out in > store. > > You must use createMemberType to create a DIType for *each*

On Jun 18, 2011, at 3:14 PM, Xi Wang wrote: > Hi, > > When generating debugging information for a data member (e.g., a struct field), Clang doesn't set the member's context to the enclosed class/struct/union type --- it currently sets the context to the file instead. The attached patch corrects this. Thanks. Do you have a test case ? Please update createMemberType() directly,

On Feb 25, 2011, at 2:28 AM, Duncan Sands wrote: > It does make me wonder how you are supposed to represent types which cannot > be properly represented by LLVM types, for example structs with fields at > variable offsets from the start and/or of variable size; or structs with > fields that may or may not be present depending on the value of other fields. > Such types occur in Ada

Hi Devang, >> It does make me wonder how you are supposed to represent types which cannot >> be properly represented by LLVM types, for example structs with fields at >> variable offsets from the start and/or of variable size; or structs with >> fields that may or may not be present depending on the value of other fields. >> Such types occur in Ada for example. >

On 24/02/11 22:34, Jason Kim wrote: > On Thu, Feb 24, 2011 at 1:29 PM, Devang Patel<dpatel at apple.com> wrote: >> 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

Hi, What could be wrong or missing in the debug info (using DIBuilder) so that a parameter is displayed well in the "Locals" window but "not found" when typing it in the "Watch" window (and not displayed in the Auto) ? Thanks ! -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 memory (register or stack) once i

Hi Paul, How can i make this call to intrinsic from the c++ code ? I'm not working with the IR language, but directly in C++ with IRBuilder::CreateAlloca. My goal is that one : - Generate machine code with an instance of the class 'IRBuilder' - Emit 'ObjFile' class instance with MCJIT - Create a DwarfContext instance directly from the emitted ObjFile object

"IR" often refers to the general concept/semantics, not only the textual format in .ll files (there are 3 main forms - bitcode, textual IR, and the in-memory representation (llvm::Module, etc - constructed using IRBuilder)). A great place to start is to look at what Clang does to produce debug info - it uses IRBuilder, for instance. So you could look at how Clang uses the IRBuilder when

Binding the alloca to the debug-info metadata is not automatic. You need to emit an intrinsic function call to llvm.dbg.declare to bind the two together. If you are simply trying to emit DWARF for your program, the rest of the processing should already be in place for that. If you are trying to do something else, you would need to describe that so we understand what you need. --paulr From:

Hi, When generating debugging information for a data member (e.g., a struct field), Clang doesn't set the member's context to the enclosed class/struct/union type --- it currently sets the context to the file instead. The attached patch corrects this. Thanks. - xi -------------- next part -------------- A non-text attachment was scrubbed... Name: clang.diff Type:

On 28/06/12 11:29, Renato Golin wrote: > On 28 June 2012 10:15, Duncan Sands <baldrick at free.fr> wrote: >>> I wanted to check that I'm headed in the right direction before I work more on >>> LLVM debug info. What I'd like to do is update DIBuilder to expose exactly the >>> facilities represented in modern DWARF, >> >> wouldn't it be

On 28 June 2012 10:15, Duncan Sands <baldrick at free.fr> wrote: >> I wanted to check that I'm headed in the right direction before I work more on >> LLVM debug info. What I'd like to do is update DIBuilder to expose exactly the >> facilities represented in modern DWARF, > > wouldn't it be better in the long term to make the debug info layer more >

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 inspect variables in GDB, it replies: (gdb) print x

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

On Sep 23, 2011, at 12:39 PM, Talin wrote: > 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

LLVM developers, Today, I made a simple change in DIBuilder interface. Now DIBuilder clients are required to use DIBuilder::finalize() to wrap up debugging information encoding for a translation unit. Relevant revisions are : r137673 and r137674 - Devang

On Oct 27, 2011, at 10:39 PM, Talin wrote: > On Mon, Oct 24, 2011 at 9:17 AM, Devang Patel <dpatel at apple.com> wrote: > > 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.) >> >>