Searched refs:addVar (Results 1 - 4 of 4) sorted by relevance

/external/valgrind/main/coregrind/m_debuginfo/
H A Dpriv_storage.h892 extern void ML_(addVar)( struct _DebugInfo* di,
H A Dstorage.c925 void ML_(addVar)( struct _DebugInfo* di, function
948 VG_(printf)(" ML_(addVar): level %d %#lx-%#lx %s :: ",
992 "warning: addVar: in range %#lx .. %#lx outside "
1018 VG_(message)(Vg_DebugMsg, "warning: addVar: %s (%s)\n",
1027 "di.storage.addVar.1",
1038 ML_(dinfo_zalloc), "di.storage.addVar.2",
1053 nyu->vars = VG_(newXA)( ML_(dinfo_zalloc), "di.storage.addVar.3",
H A Dreaddwarf3.c127 ML_(addVar) and add_var_to_arange: quite a lot of DiAddrRanges have
3749 DebugInfo; instead their contents are handed to ML_(addVar) and
4080 starting to hand variables to ML_(addVar), since if ML_(addVar)
4136 each var and hand it to ML_(addVar). */
4144 VG_(printf)("<%lx> addVar: level %d: %s :: ",
4245 /* Ok. So we're going to keep it. Call ML_(addVar) once for
4303 ML_(addVar)(
/external/clang/lib/Analysis/
H A DCFG.cpp185 void addVar(VarDecl *VD) { function in class:__anon17770::LocalScope
1269 Scope->addVar(VD);

Completed in 1940 milliseconds