Searched refs:instrumented (Results 1 – 16 of 16) 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
166 bool instrumented) { in set() argument171 instrumented_ = instrumented; in set()
101 if (!mod.instrumented()) in OnLibraryLoaded()
834 u8 uuid[kModuleUUIDSize], bool instrumented);847 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 "
199 /// Function should not be instrumented.202 /// This function should not be instrumented but it is ok to inline profiled
138 "restores them to original values when the first instrumented module is "
221 /// instrumented. Selected group numbers can be 0 to N-1 inclusive.
3118 not be inserted by ThreadSanitizer. The function is still instrumented by the3131 (e.g. by MemorySanitizer). The function may still be instrumented by the tool5777 instrumented with XRay. This will cause the function to always have space at5785 heuristics used to determine whether a function should be instrumented or
193 // code being instrumented/profiled.
1781 …HelpText<"Generate instrumented code to collect execution counts into default.profraw file (overri…1784 …HelpText<"Generate instrumented code to collect execution counts into <file> (overridden by LLVM_P…1817 …HelpText<"Generate instrumented code to collect execution counts into default.profraw (overridden …1821 …HelpText<"Generate instrumented code to collect execution counts into <directory>/default.profraw …1824 …HelpText<"Generate instrumented code to collect context sensitive execution counts into default.pr…1828 …HelpText<"Generate instrumented code to collect context sensitive execution counts into <directory…1874 …HelpText<"Generate instrumented code to collect order file into default.profraw file (overridden b…1882 …on functions into N groups and select only functions in group i to be instrumented using -fprofile…1887 … -fprofile-function-groups and select only functions in group i to be instrumented. The valid rang…2466 "emitted to unregister instrumented global variables when "[all …]
201 * functions are profiled by the instrumented code. The target addresses are
672 up tests by about 10% in the common case, hopefully more when instrumented734 common case but should help more during instrumented tests, eg under
12726 + instrumented toe.c to test memory-leaks.