HomeSort by relevance Sort by last modified time
    Searched refs:doing (Results 1 - 25 of 90) sorted by null

1 2 3 4

  /external/valgrind/none/tests/linux/
pthread-stack.stderr.exp 1 ... doing bad things till guard page
  /external/valgrind/none/tests/solaris/
pthread-stack.stderr.exp 1 ... doing bad things till guard page
  /external/valgrind/memcheck/tests/
signal2.stdout.exp 2 doing bad thing
sh-mem-random.stdout.exp 5 doing copies
  /external/valgrind/helgrind/tests/
shmem_abits.stderr.exp 4 doing many heap blocks
  /frameworks/rs/java/
Android.mk 3 # Only build our tests if we doing a top-level build. Do not build the
4 # tests if we are just doing an mm or mmm in frameworks/rs.
  /toolchain/binutils/binutils-2.25/gas/testsuite/gas/cris/
break.s 1 ; No-brainer doing an exhaustive test for this one, I guess.
  /toolchain/binutils/binutils-2.25/ld/testsuite/ld-m68hc11/
bug-1403.s 1 ;;; Bug #1403: Branch adjustment to another section not correct when doing linker relaxation
  /external/valgrind/exp-bbv/tests/amd64-linux/
fldcw_check.S 10 # fldcw is most often used to set the rouding mode when doing
  /external/valgrind/exp-bbv/tests/x86/
fldcw_check.S 10 # fldcw is most often used to set the rouding mode when doing
  /build/core/tasks/
collect_gpl_sources.mk 28 # Dist the tgz only if we are doing a full build
  /dalvik/dx/src/
Android.mk 5 # This tool is prebuilt if we're doing an app-only build.
  /frameworks/rs/api/
rs_vector_math.spec 126 The precision is what would be expected from doing the computation using 16 bit floating
144 The precision is what would be expected from doing the computation using 16 bit floating
165 The precision is what would be expected from doing the computation using 16 bit floating
  /external/dbus/tools/
dbus-monitor.c 82 oom (const char *doing)
84 fprintf (stderr, "OOM while %s\n", doing);
  /external/v8/test/webkit/
dfg-inline-unused-this-method-check.js 25 "This tests that inlining a function that does not use this does not result in this being lost entirely, if we succeed in doing method check optimizations."
dfg-intrinsic-unused-this-method-check.js 25 "This tests that doing intrinsic function optimization does not result in this being lost entirely, if method check optimizations succeed."
dfg-rshift-by-zero-eliminate-valuetoint32.js 25 "Tests that right shifting by zero and then doing other bitops doesn't eliminate the ValueToInt32 node."
resolve-arguments-from-scope.js 25 "Tests that doing repeated resolves of 'arguments' from some nested scope doesn't crash."
dfg-intrinsic-unused-this.js 25 "This tests that doing intrinsic function optimization does not result in this being lost entirely."
  /toolchain/binutils/binutils-2.25/gprof/
cg_print.c 167 Sym *todo, *doing, *prev;
174 for (doing = todo; doing != NULL; doing = todo)
176 todo = doing->cg.cyc.next;
180 if (cmp_member (doing, prev->cg.cyc.next) == GREATERTHAN)
184 doing->cg.cyc.next = prev->cg.cyc.next;
185 prev->cg.cyc.next = doing;
166 Sym *todo, *doing, *prev; local
    [all...]
  /external/chromium-trace/catapult/third_party/flot/
FAQ.md 61 it's probably because the framework you're using is doing something
  /external/v8/test/mjsunit/harmony/
async-function-stacktrace.js 100 }, ["e"]); // TODO(caitp): FuncNameInferer is doing some weird stuff...
  /external/v8/test/mjsunit/regress/
regress-1174.js 30 // Test that we do not crash when doing deoptimization of a function that has
regress-842.js 30 // since that property would be listed when doing a "for (var key in names)"
  /dalvik/dx/
Android.mk 9 # This tool is prebuilt if we're doing an app-only build.

Completed in 371 milliseconds

1 2 3 4