search for: getasmdnode

Displaying 8 results from an estimated 8 matches for "getasmdnode".

2011 Jan 05
2
[LLVMdev] Questions about debug info in LLVM 2.8
...at the various DIDescriptors contain the information I'd need, but they can only be constructed from a MDNode How do I retrieve the MDNode at the first place? Does MDNode::get() actually retrieve all the debug metadata from Module, or does it merely initialise a fresh MDNode? 2) DebugLoc has a getAsMDNode() method, but apparently it's only available for Instructions? 3) How can I retrieve a DIType instance? I can't find a way to obtain a MDNode for a Type... ? Many thanks if somebody can shed some light on this. Best regards, Jacob -------------- next part -------------- A non-text attac...
2011 Jan 06
0
[LLVMdev] Questions about debug info in LLVM 2.8
...ors contain the information I'd > need, but they can only be constructed from a MDNode How do I retrieve > the MDNode at the first place? Does MDNode::get() actually retrieve all > the debug metadata from Module, or does it merely initialise a fresh MDNode? > > 2) DebugLoc has a getAsMDNode() method, but apparently it's only > available for Instructions? > > 3) How can I retrieve a DIType instance? I can't find a way to obtain a > MDNode for a Type... ? > > Many thanks if somebody can shed some light on this. See DebugInfoFinder interface in Analysis/Debug...
2011 Jan 07
1
[LLVMdev] Questions about debug info in LLVM 2.8
...on I'd > > need, but they can only be constructed from a MDNode How do I retrieve > > the MDNode at the first place? Does MDNode::get() actually retrieve all > > the debug metadata from Module, or does it merely initialise a fresh MDNode? > > > > 2) DebugLoc has a getAsMDNode() method, but apparently it's only > > available for Instructions? > > > > 3) How can I retrieve a DIType instance? I can't find a way to obtain a > > MDNode for a Type... ? > > > > Many thanks if somebody can shed some light on this. > > See Deb...
2014 Jan 30
2
[LLVMdev] "Function" file name
Folks, I am newbie to llvm! I am writing a simple pass that inherits from ModulePass. I override the runOnModule method. In the method, i am attempting to print all the function in the module and the source-file they appear in. I could print the name of the function using the Module::iterator. I am, however, not able to figure-out the way to identify the source-file for a given
2014 Jan 24
2
[LLVMdev] How to read v3.3 dbg metadata using v3.4 LLVM
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
2013 Sep 22
0
[LLVMdev] An error when insert a function call in the IR
....so.6 0x0000003faee2bae0 __assert_perror_fail + 0 7 opt 0x0000000000b98f63 llvm::DebugLoc::getScopeAndInlinedAt(llvm::MDNode*&, llvm::MDNode*&, llvm::LLVMContext const&) const + 147 8 opt 0x0000000000b99166 llvm::DebugLoc::getAsMDNode(llvm::LLVMContext const&) const + 70 9 opt 0x0000000000c373ec llvm::Instruction::getMetadataImpl(unsigned int) const + 52 10 opt 0x0000000000c36f93 llvm::Instruction::getMetadataImpl(llvm::StringRef) const + 73 11 libLDDProfileInstrument.so 0x00007...
2010 Oct 26
0
[LLVMdev] Prevent instruction elimination
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
2010 Oct 26
2
[LLVMdev] Prevent instruction elimination
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 reached in the code generator. It seems difficult to attach >> the >> metadata to the first and the last