search for: dbg_declar

...doing a clean rebuild I get this error: /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static member function 'static bool llvm::DbgInfoIntrinsic::classof (const llvm::IntrinsicInst*)': /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: error: 'dbg_declare' is not a member of 'llvm::Intrinsic' /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static member function 'static bool llvm::DbgDeclareInst::classof (const llvm::IntrinsicInst*)': /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:172: error...

.../!= objdir)? -Chris > /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static > member function 'static bool llvm::DbgInfoIntrinsic::classof(const > llvm::IntrinsicInst*)': > /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: error: > 'dbg_declare' is not a member of 'llvm::Intrinsic' > /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static > member function 'static bool llvm::DbgDeclareInst::classof(const > llvm::IntrinsicInst*)': > /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicI...

...gt;> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In >> static member function 'static bool llvm::DbgInfoIntrinsic::classof >> (const llvm::IntrinsicInst*)': >> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: >> error: 'dbg_declare' is not a member of 'llvm::Intrinsic' >> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In >> static member function 'static bool llvm::DbgDeclareInst::classof >> (const llvm::IntrinsicInst*)': >> /Users/bocchino/llvm-checkin/src/inclu...

...kin/src/include/llvm/IntrinsicInst.h: In static > >>> member function 'static bool llvm::DbgInfoIntrinsic::classof(const > >>> llvm::IntrinsicInst*)': > >>> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: error: > >>> 'dbg_declare' is not a member of 'llvm::Intrinsic' > >>> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static > >>> member function 'static bool llvm::DbgDeclareInst::classof(const > >>> llvm::IntrinsicInst*)': > >>> /Use...

...s/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static >>> member function 'static bool llvm::DbgInfoIntrinsic::classof(const >>> llvm::IntrinsicInst*)': >>> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: error: >>> 'dbg_declare' is not a member of 'llvm::Intrinsic' >>> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In static >>> member function 'static bool llvm::DbgDeclareInst::classof(const >>> llvm::IntrinsicInst*)': >>> /Users/bocchino/llvm-che...

...;> In static >>>>> member function 'static bool llvm::DbgInfoIntrinsic::classof(const >>>>> llvm::IntrinsicInst*)': >>>>> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: >>>>> 77: error: >>>>> 'dbg_declare' is not a member of 'llvm::Intrinsic' >>>>> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: >>>>> In static >>>>> member function 'static bool llvm::DbgDeclareInst::classof(const >>>>> llvm::IntrinsicInst*...

Hi, If I have an instance of DISubprogram, can I get the debug info of local variables of the function, including parameters? I tried to use the getVariables() function defined in DISubprogram, but it seemed to return an empty DIArray node when I ran my pass alone using opt. Do I need to enable any other analysis passes in order to populate the data? My related snippet of code is like the

...gt;> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In >> static member function 'static bool llvm::DbgInfoIntrinsic::classof >> (const llvm::IntrinsicInst*)': >> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h:77: >> error: 'dbg_declare' is not a member of 'llvm::Intrinsic' >> /Users/bocchino/llvm-checkin/src/include/llvm/IntrinsicInst.h: In >> static member function 'static bool llvm::DbgDeclareInst::classof >> (const llvm::IntrinsicInst*)': >> /Users/bocchino/llvm-checkin/src/inclu...

...-O0 we save metadata space by not emitting the list and relying on the dbg_value/declare intrinsics to keep the variable metadata alive and the variables to refer to their scope (lexical blocks (that refer to subprograms) or subprograms). So you'd have to walk all the instructions looking for dbg_declare/value (I forget which, perhaps both) and trace those back to the DIVariables, etc... > > Thanks, > Lu > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.ed...

...the list and relying on >> the dbg_value/declare intrinsics to keep the variable metadata alive and >> the variables to refer to their scope (lexical blocks (that refer to >> subprograms) or subprograms). >> >> So you'd have to walk all the instructions looking for dbg_declare/value >> (I forget which, perhaps both) and trace those back to the DIVariables, >> etc... >> >> >>> >>> Thanks, >>> Lu >>> >>> >>> _______________________________________________ >>> LLVM Developers mailing lis...

> On 2014-Oct-27, at 00:58, Chandler Carruth <chandlerc at google.com> wrote: > > I haven't been able to follow all of the thread that got us here but your patch below has distilled the result enough for me to at least ask questions. Always takes a patch to draw people in :). > I'm sorry of some of the justification is buried in the thread and I'm just making you

Hi debuginfo-cabal, tl;dr: Let's please consider using a new implementation of LiveDebugValues that produces richer information, might be slightly faster, but mostly will support the instruction referencing and value tracking paradigm from my RFC [0] rather than the location tracking that LiveDebugValues does today. In that RFC, the main motivator is to treat variable locations a bit more