similar to: [LLVMdev] Debug Information Interface / Documentation

Hello, The documentation for debug information (http://llvm.org/docs/SourceLevelDebugging.html) says the structure of block descriptors metadata is: !3 = metadata !{ i32, ;; Tag = 11 + LLVMDebugVersion (DW_TAG_lexical_block) metadata,;; Reference to context descriptor i32, ;; Line number i32 ;; Column number } However, looking at the generated metadata, there are 2 extra

Hi Josh, On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote: > I'm working on generating debug information for Rust, and I'm > currently stumped on how to generate DWARF output via LLVM that will > correctly represent this (eg. when exiting from foo2(), I'd like to > see "Value returns is $1 = 5"). I'm generating debug metadata nodes > directly instead of

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

On Dec 3, 2010, at 2:39 PM, Bagel wrote: > I am writing a front end for a new language and am having trouble generating > the DWARF debugging information. I'm outputting llvm assembly source so I'm > trying to generate the "!metadata" stuff. > > I have found the document <http://llvm.org/docs/SourceLevelDebugging.html> a > helpful start, as far as it

On Nov 5, 2010, at 8:04 AM, Renato Golin wrote: > Hi All, > > We've been working on a wiki page to help people build debug > information in their own front-ends: > > http://wiki.llvm.org/Debug_Information > > It's definitely a work in progress, but it already has the basic > format and how to create the basic information (line, functions, > variables,

Unfortunately this is what I'm already doing, and it's not working. I drew inspiration from a disassembly of a program that showed that struct foo { int a; float b; char buf[80]; } struct foo get_foo(void) { foo f = { 5, 2.5 }; return f; } would turn into define void @get_foo(%struct.foo* sret %agg.result) nounwind ssp { ... call void @llvm.memcpy.p0i8.p0i8.i64(i8* %2, i8*

On Dec 6, 2011, at 4:13 PM, Devang Patel wrote: > Hi Josh, > > On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote: > >> I'm working on generating debug information for Rust, and I'm >> currently stumped on how to generate DWARF output via LLVM that will >> correctly represent this (eg. when exiting from foo2(), I'd like to >> see "Value returns

Thanks for the quick reply! I will keep the DIBuilder and Clang's CGDebugInfo as my reference for now. At the moment I want to stick with generating .ll -- it's somewhat easier for me to debug the output of my compiler that way, and I haven't programmed much in C/C++ for years -- mostly been a JVM guy. But at one point I may want to look into bindings or even creating a bootstrapped

On Wed, Mar 20, 2013 at 2:21 PM, Erkki Lindpere <villane at gmail.com> wrote: > Hi, > > I wanted to add debug info to my language (compiler written in Scala, > outputs .ll files), but I found it really hard to do based on the > documentation provided at http://llvm.org/docs/SourceLevelDebugging.html(I looked at the specific doc for LLVM 3.0 though) > > With LLVM 3.0, DI

Hi All, We've been working on a wiki page to help people build debug information in their own front-ends: http://wiki.llvm.org/Debug_Information It's definitely a work in progress, but it already has the basic format and how to create the basic information (line, functions, variables, basic types). It's not complete nor completely accurate, so if you do spot a problem, please be

Hi, I wanted to add debug info to my language (compiler written in Scala, outputs .ll files), but I found it really hard to do based on the documentation provided at http://llvm.org/docs/SourceLevelDebugging.html (I looked at the specific doc for LLVM 3.0 though) With LLVM 3.0, DI version 8 (which is documented there) seemed to work, except DW_TAG_auto_variable for which I used version tag 11

The Rust compiler defines all functions as returning void, with the first parameter being an outparam of the declared return type, ie. fn foo2() -> int { ret 5; } becomes define void @_ZN4foo217_5cb557d30658848cE(i64*, { i64, { %tydesc*, i1, {} } }*) uwtable { store i64 5, i64* %0 ret void } I'm working on generating debug information for Rust, and I'm currently stumped on how

I am writing a front end for a new language and am having trouble generating the DWARF debugging information. I'm outputting llvm assembly source so I'm trying to generate the "!metadata" stuff. I have found the document <http://llvm.org/docs/SourceLevelDebugging.html> a helpful start, as far as it goes. However, it doesn't quite match what I see clang produce

Is anyone maintaining this page? http://llvm.org/docs/SourceLevelDebugging.html#composite-type-descriptors DIBuilder::createSubroutineType seems to generate metadatas with a different format. Thanks! Wei -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130829/70facf50/attachment.html>

> On Mar 22, 2018, at 4:08 PM, Roman Levenstein <romixlev at gmail.com> wrote: > > Hi, > > I'm trying to achieve the following: > > - I have a global variable BaseAddress that holds the base address of > a contiguous dynamically allocated memory block. > > - I have a number of logical variables of different types that are > mapped on certain address

Hi, I'm trying to achieve the following: - I have a global variable BaseAddress that holds the base address of a contiguous dynamically allocated memory block. - I have a number of logical variables of different types that are mapped on certain address ranges inside the memory block pointed to by BaseAddress. The offset and the size of each such logical variable inside the memory block are

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

The debug information is actually still in a different format in the .bc file, it is LLVM metadata. I think the best reference for it is here: https://llvm.org/docs/SourceLevelDebugging.html#ccxx-frontend You can dump it just by disassembling the .bc file to textual IR using llvm-dis and examining the !DI* metadata nodes. You will have to run the file through llc to generate an object file to

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 (

On Thu, Aug 29, 2013 at 6:58 AM, Pan, Wei <wei.pan at intel.com> wrote: > Is anyone maintaining this page? ish. We sometimes forget to update it for a while. > http://llvm.org/docs/SourceLevelDebugging.html#composite-type-descriptors > > > > DIBuilder::createSubroutineType seems to generate metadatas with a different > format. composite types recently got one new