Searched refs:instrumented (Results 1 – 22 of 22) sorted by relevance
22 @ Save floating-point parameters of the instrumented function36 @ Restore floating-point parameters of the instrumented function53 @ Save the floating-point return value of the instrumented function68 @ Restore the floating-point return value of the instrumented function85 @ Save floating-point parameters of the instrumented function101 @ Restore floating-point parameters of the instrumented function
137 bool instrumented) { in set() argument141 instrumented_ = instrumented; in set()
101 if (!mod.instrumented()) in OnLibraryLoaded()
790 u8 uuid[kModuleUUIDSize], bool instrumented);801 bool instrumented() const { return instrumented_; } in instrumented() function
129 if (!flags()->use_globals && modules[i].instrumented()) continue; in ProcessGlobalRegions()
82 "Interceptors should only detect races when called from instrumented "
141 Every API call is already instrumented with an ``LLDB_RECORD_*`` macro that194 - Not all SB APIs are properly instrumented. We need customer serialization
60 The reproducer infrastructure requires API methods to be instrumented so that
133 "restores them to original values when the first instrumented module is "
169 /// Function should not be instrumented.
1177 …HelpText<"Generate instrumented code to collect execution counts into default.profraw file (overri…1180 …HelpText<"Generate instrumented code to collect execution counts into <file> (overridden by LLVM_P…1196 …HelpText<"Generate instrumented code to collect execution counts into default.profraw (overridden …1199 …HelpText<"Generate instrumented code to collect execution counts into <directory>/default.profraw …1202 …HelpText<"Generate instrumented code to collect context sensitive execution counts into default.pr…1205 …HelpText<"Generate instrumented code to collect context sensitive execution counts into <directory…1248 …HelpText<"Generate instrumented code to collect order file into default.profraw file (overridden b…1901 HelpText<"List of modes to link in by default into XRay instrumented binaries.">;1906 " even if the containing function is not always instrumented">,1912 " even if the containing function is not always instrumented">,[all …]
170 * functions are profiled by the instrumented code. The target addresses are
501 the unused function body. Hence when instrumented, all but one use of
3634 Add code so that program flow @dfn{arcs} are instrumented. During3652 This option is used to compile and link code instrumented for coverage3692 Only arcs that are not on the spanning tree have to be instrumented: the4752 range/validity tests. Modules so instrumented should be immune to4757 instrumented program is controlled by the @env{MUDFLAP_OPTIONS}13484 that function is not instrumented. The match is done on substrings:
2155 Functions with this attribute will not be so instrumented.
2617 not be inserted by ThreadSanitizer. The function is still instrumented by the2630 (e.g. by MemorySanitizer). The function may still be instrumented by the tool4945 instrumented with XRay. This will cause the function to always have space at4953 heuristics used to determine whether a function should be instrumented or
3847 (check_bct_param): Return true if loop should be instrumented.
10410 as to return the instrumented function body rather than changing the
22019 no functions are instrumented.
23360 * profile.c (instrument_edges): Return number of instrumented
9973 + instrumented toe.c to test memory-leaks.