similar to: [LLVMdev] debug calls

That's because instructions have a location associated with them, not a compile unit. -eric On Thu, Oct 4, 2012 at 12:46 PM, George Baah <georgebaah at gmail.com> wrote: > I used DILocation instead of DICompileUnit and it works. Hmmm, interesting. > > George > > On Thu, Oct 4, 2012 at 1:33 AM, George Baah <georgebaah at gmail.com> wrote: >> >> Here is

Here is the code. I am running on llvm 3.1 on Lion (Mac 10.7.4) *string getFileDirectory*(*const* Instruction &I){ MDNode *MD = I.getMetadata("dbg"); DICompileUnit compileUnit(MD); return compileUnit.getDirectory().str(); } George On Wed, Oct 3, 2012 at 12:40 PM, Eric Christopher <echristo at gmail.com>wrote: > Without knowing the code that you've written

I used DILocation instead of DICompileUnit and it works. Hmmm, interesting. George On Thu, Oct 4, 2012 at 1:33 AM, George Baah <georgebaah at gmail.com> wrote: > Here is the code. I am running on llvm 3.1 on Lion (Mac 10.7.4) > > *string getFileDirectory*(*const* Instruction &I){ > > MDNode *MD = I.getMetadata("dbg"); > > DICompileUnit

Hmmm, but it has a getDirectory function. -G On Thu, Oct 4, 2012 at 3:50 PM, Eric Christopher <echristo at gmail.com> wrote: > That's because instructions have a location associated with them, not > a compile unit. > > -eric > > On Thu, Oct 4, 2012 at 12:46 PM, George Baah <georgebaah at gmail.com> wrote: > > I used DILocation instead of DICompileUnit and

You should probably think of the DIFooBar constructors like reinterpret-casts, not "go find the thing I actually want" functions. If you hand DICompileUnit() a node that is not a compile-unit metadata node, it's not going to tell you that you goofed. If you _did_ have a CU metadata node, then DICompileUnit's getDirectory() would work just fine. But you don't. --paulr

Yeah, It looks like I am doing exactly what's in Dwarf*.cpp files, yet I am getting blanks. George On Tue, Oct 2, 2012 at 2:10 PM, Eric Christopher <echristo at gmail.com> wrote: > On Tue, Oct 2, 2012 at 11:00 AM, George Baah <georgebaah at gmail.com> wrote: > > Hi Guys, > > How does one get the directory of the compilation unit in llvm? > > I am using

Without knowing the code that you've written and the IR that you're running on I'm not sure what I can do to help you. -eric On Wed, Oct 3, 2012 at 9:32 AM, George Baah <georgebaah at gmail.com> wrote: > Yeah, It looks like I am doing exactly what's in Dwarf*.cpp files, yet I am > getting blanks. > > George > > On Tue, Oct 2, 2012 at 2:10 PM, Eric

Hi Guys, How does one get the directory of the compilation unit in llvm? I am using DICompileUnit but for some reason I am getting blanks for the directory name. Here is my code ... MDNode *MD = I.getMetadata("dbg"); DICompileUnit compileUnit(MD); *return* compileUnit.getDirectory().str(); Thanks George -------------- next part -------------- An HTML attachment was scrubbed...

On Tue, Oct 2, 2012 at 11:00 AM, George Baah <georgebaah at gmail.com> wrote: > Hi Guys, > How does one get the directory of the compilation unit in llvm? > I am using DICompileUnit but for some reason I am getting blanks > for the directory name. Here is my code ... > > MDNode *MD = I.getMetadata("dbg"); > > DICompileUnit compileUnit(MD); > > return

Hi All, Today, debugging information is encoded in LLVM IR using various llvm.dbg intrinsics, such as llvm.dbg.stoppoint. For exmaple, !1 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c", metadata !"/tmp", metadata !"clang 1.0", i1 true, i1 false, metadata !"", i32 0} ... call void @llvm.dbg.stoppoint(i32 5, i32 5, metadata !1) store i32

Hi Everyone, I am processing instructions in a module and I would like to avoid "call void @llvm.dbg.declare ..." instructions as they just provide debug info about a given instruction. Is there a way to avoid these instructions without having to turn off the -g option? Thanks. George -------------- next part -------------- An HTML attachment was scrubbed... URL:

Devang Patel wrote: > Hi Richard, > > How do you produce this LLVM assembly? In newest form, > llvm.dbg.func_start intrinsic is not used. > - > Devang > Hi Devang, The assembly is disassembled from bitcode that I create. I must be using obsolete remnants of the API. I'm calling EmitFunctionStart(), EmitStopPoint(), etc. What should I be using? -Rich

I've opened PR 12050 to track the problem with llvm.dbg.gv Eli From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Bendersky, Eli Sent: Tuesday, February 14, 2012 13:45 To: Devang Patel; Eric Christopher Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] generating !llvm.dbg.sp Eric, Devang, FYI exactly the same applies for llvm.dbg.gv - it's also

Thanks Eric. I know some of the references are in the code used for backward compatibility. - Devang On Feb 13, 2012, at 9:21 AM, Eric Christopher <echristo at apple.com> wrote: > Thanks. I'll get them. :) > > -eric > > On Feb 13, 2012, at 1:41 AM, Bendersky, Eli wrote: > >> Thanks. Note that there are still a few references to this MDNode scattered throughout

Eric, Devang, FYI exactly the same applies for llvm.dbg.gv - it's also still listed in the docs and in various places throughout the code, although no longer generated. Eli From: Devang Patel [mailto:dpatel at apple.com] Sent: Monday, February 13, 2012 19:26 To: Eric Christopher Cc: Bendersky, Eli; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] generating !llvm.dbg.sp Thanks Eric. I know

I mean an llvm Pass that transforms switch statements into if statements. For example, if I have code with switch statements then running the pass will convert all switches to ifs in the bytecode. George On Mon, May 6, 2013 at 4:20 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "George Baah" <georgebaah at gmail.com> > >

Suppose I have fun.h as: static void fun() { int a =10; } Now I have two files foo.c and goo.c as foo.c : #include "fun.h" void foo() { fun(); } goo.c: #include "fun.h" void goo() { fun(); } I get .bc files for foo.c and foo.bc through clang. Now I run llvm-ld with -disable-opt for foo.bc and goo.bc. In the resulting .bc files, one of the

On Feb 6, 2011, at 8:52 PM, sivakumar srinivasan wrote: > Hi Everyone, > > I am really new to LLVM. I am working on something where I had to pick-up a half-cooked backend and need to add debug support to it. I have searched through messages but could not find a nice starting place. Could some one please provide me with some pointers about > - what is already supported in llvm as far

>> There are a couple of references made to %llvm.dbg.variable, which >> isn't defined anywhere. It it an intrinsic? A global? Could it be a >> relic from the old debug info docs (where it *is* defined?). The same >> goes for llvm.dbg.derivedtype and llvm.dbg.subrange which are also >> referenced but not defined. > > It was a stale reference. I fixed the

Thanks. Note that there are still a few references to this MDNode scattered throughout the code-base, so if it's no longer being generated, there may be some bugs lurking there. Eli From: Devang Patel [mailto:dpatel at apple.com] Sent: Thursday, February 09, 2012 19:36 To: Bendersky, Eli Cc: llvmdev at cs.uiuc.edu Subject: Re: generating !llvm.dbg.sp On Feb 9, 2012, at 7:17 AM,