similar to: [LLVMdev] "Function" file name

Hi, I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able to extract the debug info produced by LLVM-GCC and stored in the compiled .bc file. However I admit I'm slightly confused about how exactly to do that, the documentation doesn't seem to be very clear about this, it mainly describes how to *generate* debug info. Specifically I'm wondering about the

On Jan 4, 2011, at 7:32 PM, Jacob Zimmermann wrote: > Hi, > > I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able > to extract the debug info produced by LLVM-GCC and stored in the > compiled .bc file. However I admit I'm slightly confused about how > exactly to do that, the documentation doesn't seem to be very clear > about this, it mainly

On Thu, 2011-01-06 at 11:13 -0800, Devang Patel wrote: > On Jan 4, 2011, at 7:32 PM, Jacob Zimmermann wrote: > > > Hi, > > > > I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able > > to extract the debug info produced by LLVM-GCC and stored in the > > compiled .bc file. However I admit I'm slightly confused about how > >

Thanks Eric, but could you give me a little bit more hints or pointers please? I looked into DebugInfo.h, but I'm still not sure how to start. It sounds like I'd have to somehow manually extract metadata nodes from an instruction. Thanks, JS On Wed, Jan 22, 2014 at 10:14 PM, Eric Christopher <echristo at gmail.com>wrote: > This is likely going to be difficult if possible. I

Hi Ben, That did help. I continue to notice the virtual register in the program. I use LLVM 3.4. The program i am looking at is a very simple one. Listed below int global_var; int *global_ptr; int32_t main(int32_t argc, char ** argv){ int p = 10; int k = 20; int *pp; char *c_pp; pp = &k; global_ptr = pp; pp = &p; global_ptr = &global_var; return 0; } BR/Nizam

Hi Tim, Assume a store instruction. Store has 2 Operands. I can use the store->getOperand(0) and store->getOperand(1) methods to access these operands in form of Value *. Very likely that the operands are stack variables or formal variables or global variables. It is also possible that these operands are LLVM virtual-registers. Is there a way to determine if a given operand is a

Thanks Sean. It clarified my query. Do you have an answer to my other question (in a different mail-chain) listed below Is there a simple way to check if a given instruction operand (represented by Value *) is a virtual register or otherwise? Context: I am creating a ModulePass for pointer Analysis. BR/Nizam From: "Sean Silva" <chisophugis at gmail.com> To: nizam

Török Edwin wrote: > [snip] > > Ah, the method got moved to the instruction itself! > > dbgKind = Context->getMDKindID("dbg"); > if (MDNode *Dbg = I->getMetadata(dbgKind)) { > ... > Thanks! This appears to work. I also have code that looks up debug information for GlobalVariables and regular LLVM Value *'s. For the former, I think I can look up

Hi, is there a opt pass that replaces the SSA virtual registers to stack-variables? I want to eliminate the SSA virtual register from my IR. Kindly suggest BR/Nizam -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140201/bdc3909a/attachment.html>

Hi all, I am wondering if someone can give me pointers to how to use the DI* classes defined in DebugInfo.h. In particular, I am confused about how to get a MDNode from the GlobalVariable's that hold the debug info so that they can be passed into the DI* classes, and the difference between MDNode and NamedMDNode in general. Thanks for your help. Alvin

Folks, I have a LLVM instruction like the following %0 = load i32** %pp, align 8 I have a LoadInst &inst handle to this instruction. In addition, i could access the pointer being loaded from using the inst.getPointerOperand... However, is there a way to access the handle to the value being loaded? Essentially, i wanted to access the %0 in the statement listed. The end goal is

On Mon, Sep 21, 2009 at 9:34 PM, Alvin Cheung <alvin.cheung at gmail.com> wrote: > Hi all, > > I am wondering if someone can give me pointers to how to use the DI* classes > defined in DebugInfo.h.  In particular, I am confused about how to get a MDNode > from the GlobalVariable's that hold the debug info so that they can be passed > into the DI* classes, Now, MDNode

Török Edwin wrote: > [snip] >>> Something like this (you can of course cache TheMetadata and MDDbgKind) >>> >>> llvm::MetadataContext *TheMetadata = M->getContext().getMetadata(); >>> MDDbgKind = TheMetadata->getMDKind("dbg"); >>> if (MDDbgKind) { >>> if (MDNode *Dbg = TheMetadata->getMD(MDDbgKind, I)) { >>>

On Sun, Nov 17, 2013 at 6:35 PM, Manman Ren <manman.ren at gmail.com> wrote: > Hi Bill, > > Thanks for the testing case. Most of the time is spent on debug info > verifier. > I fixed a bug in r194974, now it takes too long to run debug info > verification. > > Debug info verifier is part of the verifier which is a Function Pass. Tot > currently tries to pull all

On Mon, Nov 18, 2013 at 10:55 AM, Eric Christopher <echristo at gmail.com>wrote: > On Sun, Nov 17, 2013 at 6:35 PM, Manman Ren <manman.ren at gmail.com> wrote: > > Hi Bill, > > > > Thanks for the testing case. Most of the time is spent on debug info > > verifier. > > I fixed a bug in r194974, now it takes too long to run debug info > >

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,

I think it might be. I’m attaching a preprocessed file that can show the problem. Compile it with ToT. $ clang++ -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -m64 -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcovered-switch-default -Wno-uninitialized -Wno-missing-field-initializers -c

Hi Bill, Thanks for the testing case. Most of the time is spent on debug info verifier. I fixed a bug in r194974, now it takes too long to run debug info verification. Debug info verifier is part of the verifier which is a Function Pass. Tot currently tries to pull all reachable debug info MDNodes in each function, which is too time-consuming. The correct fix seems to be separating debug info

Hi, I'm trying to recover the inheritance relations for a class type (so a list of base classes) from a llvm ir file generated via compiling some cpp file using clang. I have access to the TypeSymbolTable and have found the class type I want to know the base classes for in the table. How do I go about extracting this (debug) information? I'm stuck here: if(StructType*

On Oct 26, 2010, at 9:23 AM, Xinfinity wrote: > > Hello, > > > Devang Patel wrote: >> >> >> On Oct 25, 2010, at 12:09 PM, Xinfinity wrote: >> >>> #pragma my_pragma{ >>> code >>> } >> >>> I use a map >>> (source_location, pragma) and I insert the dummy instruction when this >>> location is