Searched refs:Callers (Results 1 – 18 of 18) sorted by relevance
34 MallocMap *Callers; variable37 if (Callers != nullptr && !InAllocatorFunction) { in internalAllocator()39 ++(*Callers)[caller]; in internalAllocator()74 Callers = new MallocMap(); in LinuxMallocProfiling()78 if (Callers == nullptr) { in ~LinuxMallocProfiling()81 for (const auto &C : *Callers) { in ~LinuxMallocProfiling()93 delete Callers; in ~LinuxMallocProfiling()94 Callers = nullptr; in ~LinuxMallocProfiling()
81 static void collectCallers(Function *F, DenseSet<Function *> &Callers) { in collectCallers() argument85 if (Callers.insert(Caller).second) in collectCallers()86 collectCallers(Caller, Callers); in collectCallers()107 DenseSet<Function *> Callers; in runOnModule() local134 collectFunctionUsers(UU, Callers); in runOnModule()145 for (auto F : Callers) { in runOnModule()
569 CallerSym Callers(SymbolRecordKind::CallerSym); in TEST_F() local570 Callers.Indices.push_back(TypeIndex(4)); in TEST_F()571 Callers.Indices.push_back(TypeIndex(5)); in TEST_F()572 Callers.Indices.push_back(TypeIndex(6)); in TEST_F()577 writeSymbolRecords(Callees, Callers, Inlinees); in TEST_F()
17 total := runtime.Callers(1, pcs)
31 CHECK-NEXT: Callers [
50 Callers must ensure all the named tensors are indeed stored in the checkpoint.
40 error occurs while writing a cache value, the edit will fail silently. Callers
115 Callers will typically cast the result pointer into the appropriate
210 release the object before returning. Callers that wish to independently retain a212 transferring. Callers should also take note of whether the function is
76 Callers of this must call :c:func:`PyFile_DecUseCount` when they are
139 n := runtime.Callers(2, el.stack)
296 // This is so users can compare against null. Callers should be able
67 …hod 'getViolation' is potentially leaked when using garbage collection. Callers of this method do…72 …od 'copyViolation' is potentially leaked when using garbage collection. Callers of this method do…1207 …getViolation' is potentially leaked when using garbage collection. Callers of this method do…1209 …getViolation' is potentially leaked when using garbage collection. Callers of this method do…1394 …opyViolation' is potentially leaked when using garbage collection. Callers of this method do…1396 …opyViolation' is potentially leaked when using garbage collection. Callers of this method do…
716 group: utrie # Callers should use ucptrie instead.
1104 // Callers do best to use "random-looking" values for a and b.
379 # Callers can only provide two parameters and optionally pass _cache by keyword
525 # Callers will never provide a third parameter for this function.
2667 by the caller using free() when the memory region is no longer needed. Callers