search for: md_dbg

...the relationship >> between constant, globals and related debuginfo, metadata information? > To get to the source variables associated with a global you can use code like this (copied from the IR Verifier): > > SmallVector<MDNode *, 1> MDs; > GV.getMetadata(LLVMContext::MD_dbg, MDs); > for (auto *MD : MDs) { > if (auto *GVE = dyn_cast<DIGlobalVariableExpression>(MD)) > // do stuff. > > -- adrian > >> I would appreciate it for any help. >> In advance, thank you very much. >> >> -- >> ----------------------...

Hello LLVM Community, I'm working on some analyzer\checker and want to implement checker for variables. In that case, I want to retrieve some information about types of variables or identify that the variable is either string or not. As an example, for strings which can be char or string type I came up with a solution to find it out via isString or isCString methods. But for strings whose

Am 20.01.2012 um 18:12 schrieb Devang Patel: > > On Jan 19, 2012, at 10:12 AM, Christian Jacobs wrote: > >> Hello, >> I need to know how I get the LLVM::IDScope object of an instruction. >> >> My program contains: >> call void (...)* @commit(), !dbg !16 >> >> !16 = metadata !{i32 16, i32 5, metadata !8, null} >> >> !8 = metadata

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

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