Home
last modified time | relevance | path

Searched refs:runs (Results 1 – 25 of 35) sorted by relevance

12

/ndk/sources/cxx-stl/llvm-libc++/libcxx/test/thread/thread.condition/thread.condition.condvarany/
Dwait_for.pass.cpp34 int runs = 0; variable
49 if (runs == 0) in f()
59 ++runs; in f()
Dwait_for_pred.pass.cpp44 int runs = 0; variable
57 if (runs == 0) in f()
67 ++runs; in f()
Dwait_until.pass.cpp51 int runs = 0; variable
64 if (runs == 0) in f()
74 ++runs; in f()
Dwait_until_pred.pass.cpp62 int runs = 0; variable
74 if (runs == 0) in f()
86 ++runs; in f()
/ndk/sources/cxx-stl/llvm-libc++/libcxx/test/thread/thread.condition/thread.condition.condvar/
Dwait_for.pass.cpp31 int runs = 0; variable
46 if (runs == 0) in f()
56 ++runs; in f()
Dwait_for_pred.pass.cpp41 int runs = 0; variable
54 if (runs == 0) in f()
64 ++runs; in f()
Dwait_until.pass.cpp48 int runs = 0; variable
61 if (runs == 0) in f()
71 ++runs; in f()
Dwait_until_pred.pass.cpp58 int runs = 0; variable
70 if (runs == 0) in f()
82 ++runs; in f()
/ndk/sources/host-tools/make-3.81/tests/scripts/features/
Derrors7 $details = "This test runs two makes. The first runs on a target with a \n"
/ndk/sources/host-tools/make-3.81/tests/scripts/variables/
DSHELL21 # makefile, but make runs $(SHELL) -c 'commandline' and that doesn't work at
/ndk/tests/device/test-stlport/unit/
Dunordered_test.cpp434 for (int runs = 0; runs < 2; ++runs) { in equal_range() local
/ndk/tests/device/test-gnustl-full/unit/
Dunordered_test.cpp434 for (int runs = 0; runs < 2; ++runs) { in equal_range() local
/ndk/sources/third_party/googletest/googletest/
DCHANGES82 * New feature: when a test runs under Visual Studio, its failures are
/ndk/sources/host-tools/make-3.81/glob/
DChangeLog109 on the compile line. This is because when build.sh runs it merely
/ndk/sources/host-tools/make-3.81/
DNEWS441 are now omitted if Make runs no commands and has no other messages to print.
519 * The exit status of Make when it runs into errors is now 2 instead of 1.
627 the current directory before and after Make runs. The `-C' switch to
645 Make runs. Instead, only variables specified on the command line or in
DCOPYING164 operating system on which the executable runs, unless that component
/ndk/sources/third_party/googletest/googletest/include/gtest/
Dgtest-param-test.h.pump202 // with a particular generator, Google Test creates and runs tests
/ndk/build/tools/toolchain-licenses/
DCOPYING163 operating system on which the executable runs, unless that component
/ndk/tests/device/test-stlport_static-exception/
DCOPYING163 operating system on which the executable runs, unless that component
/ndk/sources/host-tools/make-3.81/tests/
DCOPYING163 operating system on which the executable runs, unless that component
/ndk/sources/host-tools/ndk-stack/
DNOTICE163 operating system on which the executable runs, unless that component
/ndk/tests/build/lambda-defarg3/
DCOPYING163 operating system on which the executable runs, unless that component
/ndk/tests/device/test-stlport_shared-exception/
DCOPYING163 operating system on which the executable runs, unless that component
/ndk/tests/build/test-stlport_static-exception-force-rebuild/
DCOPYING163 operating system on which the executable runs, unless that component
/ndk/sources/host-tools/make-3.81/doc/
Dmake.info-1245 * Make Control Functions:: Functions that control how make runs.
1229 succeeds in making one, or it runs out of names to try. Note that it
1838 part is the so-called drive letter). When `make' runs on these
3273 actually installed on the system where `make' runs.
3428 date, so the next time `make' runs, it will not try to update that
3853 The first command in this example runs Yacc on the first
4679 When `make' runs a command script, variables defined in the makefile
5117 * Make Control Functions:: Functions that control how make runs.
6003 These functions control the way make runs. Generally, they are used to
6363 `CFLAGS' is included in each command that runs the C compiler, so a
[all …]

12