/external/chromium-trace/trace-viewer/src/about_tracing/ |
profiling_view.css | 6 .profiling-view { 13 .profiling-view .controls .save { 17 .profiling-view > .container { 22 .profiling-overlay { 28 .profiling-overlay .raw-text { 33 .profiling-overlay .error {
|
/external/chromium/chrome/browser/resources/gpu_internals/ |
profiling_view.css | 6 #profiling-view { 12 #profiling-view[selected] { 16 #profiling-view > .control { 21 #profiling-view > .container { 27 .profiling-overlay { 33 .profiling-overlay .raw-text { 39 .profiling-overlay .error {
|
/dalvik/vm/mterp/armv5te/ |
entry.S | 72 cmp r0,#0 @ is profiling disabled? 74 bne common_updateProfile @ profiling is enabled 77 beq 1f @ profiling is disabled
|
/dalvik/vm/mterp/mips/ |
entry.S | 61 bnez a0, common_updateProfile # profiling is enabled 64 beqz a0, 1f # profiling is disabled
|
/external/chromium_org/third_party/jstemplate/ |
jstemplate_example.js | 26 * Are we actively profiling JstProcessor? 29 var profiling = false; variable 63 if (profiling) Profiler.reset(); 65 if (profiling) Profiler.dump(); 79 if (profiling) Profiler.reset(); 81 if (profiling) Profiler.dump(); 91 if (profiling) Profiler.reset(); 93 if (profiling) Profiler.dump(); 109 if (profiling) Profiler.reset(); 111 if (profiling) Profiler.dump() [all...] |
/external/chromium_org/base/allocator/ |
allocator_shim.cc | 296 const char* profiling = local 298 if (profiling && *profiling == '1') {
|
/frameworks/av/services/audioflinger/ |
test-resample.cpp | 67 fprintf(stderr," -p enable profiling\n"); 84 bool profiling = false; local 95 profiling = true; 212 if (profiling) {
|
/packages/inputmethods/LatinIME/native/jni/ |
Android.mk | 108 $(warning Making profiling version of native library) 135 $(warning Making profiling version of native library)
|
/external/chromium_org/third_party/tcmalloc/vendor/packages/rpm/ |
rpm.spec | 22 malloc() and cpu and heap profiling utilities.
|
/external/chromium_org/v8/test/mjsunit/ |
count-based-osr.js | 30 // Test that OSR works properly when using count-based interrupting/profiling.
|
/external/chromium_org/v8/test/webkit/ |
new-array-double-with-holes.js | 25 "Tests that if array allocation profiling causes a new_array to allocate double arrays, then the holes end up being correctly initialized."
|
dfg-constant-fold-misprediction.js | 43 // process of correcting predictions (OSR exit profiling, exiting to profiled code,
|
/external/v8/test/mjsunit/ |
count-based-osr.js | 30 // Test that OSR works properly when using count-based interrupting/profiling.
|
/external/chromium_org/content/app/ |
content_main_runner.cc | 586 const char* profiling = getenv(tracked_objects::kAlternateProfilerTime); variable 587 if (profiling && 588 (atoi(profiling) == tracked_objects::TIME_SOURCE_TYPE_TCMALLOC)) {
|
/external/chromium_org/third_party/WebKit/Source/devtools/front_end/ |
profilesPanel.css | 161 .control-profiling {
|
/dalvik/vm/compiler/template/armv5te/ |
footer.S | 26 beq 121f @ hop if not profiling
|
/dalvik/vm/ |
Android.mk | 118 # need this for clock_gettime() in profiling
|
Dvm.mk | 51 # - profiling enabled 73 # - (debugging and profiling still enabled)
|
/external/oprofile/utils/ |
opcontrol | 142 --start-daemon start daemon without starting profiling 144 -d/--dump flush the collected profiling data 177 profiling. 199 --active-domains=<list> List of domains in profiling session (for Xen) 830 echo "Call-graph profiling unsupported on this kernel/hardware" >&2 987 echo "Stopping profiling." 1082 # VMs may already be running when profiling is started, so 1251 # check if event is SPU Event profiling 1256 echo "SPU event profiling not compatible with any other event" 1261 # profiling. Note, if the file exits it should hav [all...] |
/frameworks/base/core/java/android/view/ |
HardwareRenderer.java | 87 * System property used to enable or disable hardware rendering profiling. 90 * When profiling is enabled, the adb shell dumpsys gfxinfo command will 95 * "true", to enable profiling 96 * "visual_bars", to enable profiling and visualize the results on screen 97 * "visual_lines", to enable profiling and visualize the results on screen 98 * "false", to disable profiling 109 * value, profiling data will be visualized on screen as a bar chart. 117 * value, profiling data will be visualized on screen as a line chart. 125 * when doing hardware rendering profiling. 128 * When profiling is enabled, the adb shell dumpsys gfxinfo command wil 902 String profiling = SystemProperties.get(PROFILE_PROPERTY); local [all...] |
/external/antlr/antlr-3.4/runtime/Ruby/lib/antlr3/ |
profile.rb | 191 Profiler is an event-listener that performs all of the profiling accounting and
|
debug.rb | 101 generated in debug or profiling mode.
|
/external/compiler-rt/make/platform/ |
clang_darwin.mk | 66 # Configurations which define the profiling support functions.
|
/external/valgrind/main/none/tests/ |
cmdline2.stdout.exp | 99 --profile-flags=<XXXXXXXX> ditto, but for profiling (X = 0|1) [00000000]
|
/frameworks/base/core/java/android/app/ |
ActivityThread.java | 435 boolean profiling; field in class:ActivityThread.Profiler 438 if (profiling) { 459 if (profileFd == null || profiling) { 465 profiling = true; 467 Slog.w(TAG, "Profiling failed on path " + profileFile); 477 if (profiling) { 478 profiling = false; [all...] |