Searched refs:instrumented (Results 1 – 18 of 18) sorted by relevance
32 # The registers r2-15 of the instrumented function are already saved in the34 # of the first instruction of the instrumented function.68 # The registers r2-15 of the instrumented function are already saved in the70 # of the first instruction of the instrumented function.106 # The registers r2-15 of the instrumented function are already saved in the109 # which contains the return address into the caller of the instrumented142 # The registers r2-15 of the instrumented function are already saved in the145 # which contains the return address into the caller of the instrumented
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
166 bool instrumented) { in set() argument171 instrumented_ = instrumented; in set()
104 if (!mod.instrumented()) in OnLibraryLoaded()
844 u8 uuid[kModuleUUIDSize], bool instrumented);857 bool instrumented() const { return instrumented_; } in instrumented() function
148 if (!flags()->use_globals && modules[i].instrumented()) continue; in ProcessGlobalRegions()
76 "Interceptors should only detect races when called from instrumented "
234 /// Function should not be instrumented.237 /// This function should not be instrumented but it is ok to inline profiled
141 "restores them to original values when the first instrumented module is "
193 // code being instrumented/profiled.
224 /// instrumented. Selected group numbers can be 0 to N-1 inclusive.
3618 not be inserted by ThreadSanitizer. The function is still instrumented by the3630 (e.g. by MemorySanitizer). The function may still be instrumented by the tool6542 instrumented with XRay. This will cause the function to always have space at6550 heuristics used to determine whether a function should be instrumented or6888 1. Indirect calls to a function type with this attribute will not be instrumented with CFI. That is,
1748 …HelpText<"Generate instrumented code to collect coverage info for cold functions into default.prof…1751 …HelpText<"Generate instrumented code to collect coverage info for cold functions into <directory>/…1754 HelpText<"Generate instrumented code to collect temporal information">;1757 …HelpText<"Generate instrumented code to collect execution counts into default.profraw file (overri…1760 …HelpText<"Generate instrumented code to collect execution counts into <file> (overridden by LLVM_P…1793 …HelpText<"Generate instrumented code to collect execution counts into default.profraw (overridden …1797 …HelpText<"Generate instrumented code to collect execution counts into <directory>/default.profraw …1800 …HelpText<"Generate instrumented code to collect context sensitive execution counts into default.pr…1804 …HelpText<"Generate instrumented code to collect context sensitive execution counts into <directory…1861 …on functions into N groups and select only functions in group i to be instrumented using -fprofile…[all …]
201 * functions are profiled by the instrumented code. The target addresses are
8757 up tests by about 10% in the common case, hopefully more when instrumented8819 common case but should help more during instrumented tests, eg under
14923 + instrumented toe.c to test memory-leaks.