similar to: [LLVMdev] llvm dwarf emission

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] llvm dwarf emission"

2012 Jun 28
0
[LLVMdev] llvm dwarf emission
Hi Nick, > 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 abstract rather than a direct mapping onto dwarf? Ciao, Duncan. and to store that in
2003 Apr 29
4
Bug in g++ 2.95.4 (Pointer to member functions)
Hi, I think I have discovered a bug in FreeBSD 4.8-STABLE's system C++ compiler: % gcc -v % Using builtin specs. % gcc version 2.95.4 20020320 [FreeBSD] Here is a stripped down example that can be used to reproduce the bug: // ----------- begin bug.cpp ----------- #include <iostream> class Class { public: void M1 (void) { cout << "M1" << endl; }; void M2
2012 Jun 28
2
[LLVMdev] llvm dwarf emission
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 >
2011 Apr 04
0
[LLVMdev] More DWARF problems
Talin, You're developing your own language and tool sets, it brings fresh perspective in our predominately C orientated environment, which is good. On Apr 1, 2011, at 8:12 PM, Talin wrote: > Is this a limitation of DWARF or of the LLVM generator? Neither, IMO. My own reading of DWARF did not find clear wording on this subject. I am not even sure if it is just a darwin gdb implementation
2011 Apr 02
2
[LLVMdev] More DWARF problems
On Thu, Mar 31, 2011 at 9:15 AM, Devang Patel <dpatel at apple.com> wrote: > > On Mar 31, 2011, at 12:57 AM, Talin wrote: > > On Wed, Mar 30, 2011 at 11:17 AM, Devang Patel <dpatel at apple.com> wrote: > >> >> On Mar 29, 2011, at 7:29 PM, Talin wrote: >> >> I've been trying to track down the problem with the DWARF info that is >> being
2012 Jun 28
0
[LLVMdev] llvm dwarf emission
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
2018 Mar 31
2
[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 use DIBuilder::createAutoVariable and how ? Then, I'm wondering how to locate back my local variable in memory (register or stack) once i
2018 Apr 01
0
[Dwarf] Register a local variable in DIBuilder and locate it later with a DwarfContext
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:
2011 Feb 19
3
[LLVMdev] DIFactory
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.
2018 Aug 22
2
[DebugInfo] DIBuilder missing interface to generate DWARF info for packed_decimal basic type.
Adding tags on subject line From: Chirag Patel Sent: 22 August 2018 11:20 To: llvm-dev at lists.llvm.org Subject: DIBuilder missing interface to generate DWARF info for packed_decimal basic type. Hello, I am working on a llvm based compiler frontend in which, I am using the packed_decimal type encoding. During using the llvm DIBuilder, I found out that the interface to create BasicType with
2018 Apr 01
2
[Dwarf] Register a local variable in DIBuilder and locate it later with a DwarfContext
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
2018 Apr 02
0
[Dwarf] Register a local variable in DIBuilder and locate it later with a DwarfContext
"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
2011 Feb 21
0
[LLVMdev] DIFactory
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 meant to use for
2011 Feb 18
1
[LLVMdev] DIFactory
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.
2018 Aug 23
4
[DebugInfo] DIBuilder missing interface to generate DWARF info for packed_decimal basic type.
Hello Paul, Thanks for the reply. Yes, I am only looking for dwarf support at the moment and planning to support both PLI/COBOL decimal types. Also thanks for the suggestion, you are right as it is going to be rare cases, so it will be better to implement a separate subclass to avoid memory overhead for others. >> (Somebody is actively working on scaled binary operations, although they
2011 Feb 21
2
[LLVMdev] DIFactory
On 21 February 2011 18:17, Devang Patel <dpatel at apple.com> wrote: > TheCU is an internal debug info information that FE should not care about. DIBuilder is meant to use for one translation unit by FE. If all the internal debug info information is exposed to FE then you'll get DIFactory. I agree, DIBuilder should not expose its internal structure. This is why, on a C-only world,
2011 Mar 17
2
[LLVMdev] Writing unit tests for DWARF?
Renato, On Mar 17, 2011, at 3:25 AM, Renato Golin wrote: > could help with the verification process (since it's much better to > fail verification than to fail gdb testuite), but I don't know the > design decisions being taken for debug information/metadata, and they > change too frequently to dig the code to learn. I think you are mistaken here. I maintain and support
2012 Aug 21
1
[LLVMdev] Dwarf debug info misses while clang codegen
I'm trying to write a llvm pass to add debug info into a non-debug-info bitcode file. I have been read http://llvm.org/docs/SourceLevelDebugging.html. And I use DIBuilder to produce the debug metadata. I know I can't get all information form ir code . So I add some manual info as test data. After executing my pass, I can find debug info metadata in my generated bitcode. Those metadata
2011 Mar 17
0
[LLVMdev] Writing unit tests for DWARF?
On 17 March 2011 13:48, Devang Patel <dpatel at apple.com> wrote: > I think you are mistaken here. I maintain and support debug info for two front ends (llvm-gcc and clang). Go ahead and check svn archives for last one year and see how many times I had to update llvm-gcc FE. Hi Devang, First, I'm not attacking anyone. I said before and will say again: the work you've done is
2014 Apr 28
2
[LLVMdev] Feeding DWARF debug information for an LLVM module
I'm trying to insert some DWARF debugging information into a LLVM IR module by manually parsing the DWARF debug DIEs. I'm doing it that way since I wrote my custom front-end for my language and the DWARF debugging information are provided me as a byte stream for the various DWARF sections. I took a look at the documentation and DwarfDebug class (