/toolchain/binutils/binutils-2.25/gas/testsuite/gas/arm/ |
t16-bad.s | 1 @ Things you can't do with 16-bit Thumb instructions, but you can
|
/external/valgrind/none/tests/amd64/ |
ssse3_misaligned.stderr.exp | 0 you should see: "one\ntwo\nthree\n"
|
/external/valgrind/none/tests/x86/ |
ssse3_misaligned.stderr.exp | 0 you should see: "one\ntwo\nthree\n"
|
/external/droiddriver/ |
contributing_aosp.md | 5 Follow instructions at https://source.android.com/source/downloading.html except those noted below. You need to set up authentication to be able to submit changes. 6 DroidDriver is an "unbundled" project. If you specify the repo manifest branch "droiddriver-dev" (see below), you'll get only the relevant projects instead of the whole AOSP tree. 18 The code should be downloaded to the current dir. You may see some lines in the output like: 20 These messages seem non-fatal and you should see these dirs after it is done: 42 The '<>' above are literal. The emails must have been registered with Gerrit. You can also use the "--cc" flag. 66 ManualDD is an APK you can use to manually test DroidDriver.
|
/external/antlr/antlr-3.4/runtime/Perl5/lib/ANTLR/Runtime/ |
TokenSource.pm | 7 # until you get a good one; errors are not passed through to the parser. 10 # Where are you getting tokens from? normally the implication will simply 28 Errors from the lexer are never passed to the parser. Either you want 29 to keep going or you do not upon token recognition error. If you do not 30 want to continue lexing then you do not want to continue parsing. Just 32 toss you all the way out of the recognizers. If you want to continue 33 lexing then you should not throw an exception to the parser--it has already 34 requested a token. Keep lexing until you get a valid one. Just repor [all...] |
/external/icu/icu4c/source/data/translit/ |
trnsfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'trnslocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or re
|
/external/chromium-trace/catapult/third_party/flot/ |
FAQ.md | 5 Flot will happily draw everything you send to it so the answer 8 if IE users are in your target group (for large plots in IE, you can 11 1000 points is not a problem, but as soon as you start having more 12 points than the pixel width, you should probably start thinking about 14 chart anyway. If you downsample server-side, you also save bandwidth. 19 Actually, Flot loves JSON data, you just got the format wrong. 20 Double check that you're not inputting strings instead of numbers, 28 You can grab the image rendered by the canvas element used by Flot 31 doesn't work with excanvas which uses VML, but you could tr [all...] |
/toolchain/binutils/binutils-2.25/ld/testsuite/ld-pe/ |
export_dynamic_warning.d | 4 #warning: warning: --export-dynamic is not supported for PE\+? targets, did you mean --export-all-symbols\?
|
/toolchain/binutils/binutils-2.25/gas/testsuite/gas/nios2/ |
warn_nobreak.l | 3 If you don't need to debug this code use .set nobreak to turn off this warning. 5 If you don't need to debug this code use .set nobreak to turn off this warning. 7 If you don't need to debug this code use .set nobreak to turn off this warning. 9 If you don't need to debug this code use .set nobreak to turn off this warning.
|
/external/icu/icu4c/source/data/misc/ |
miscfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'misclocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or re-
|
/external/icu/icu4c/source/data/sprep/ |
sprepfiles.mk | 6 # If you are thinking of modifying this file, READ THIS. 8 # Instead of changing this file [unless you want to check it back in], 9 # you should consider creating a 'brklocal.mk' file in this same directory. 10 # Then, you can have your local changes remain even if you upgrade or
|
/external/mdnsresponder/mDNSShared/ |
dnsextd.conf | 5 // In most cases, you should not need to change these default options in 9 // You need to edit the "zone" statement below to give the name of your 16 // In /etc/named.conf you will need to modify the "options" section to 21 // You also need a "zone" statement in /etc/named.conf to tell BIND the update 23 // network, you might allow anyone to perform updates. To do that, you just 30 // you'll want to limit updates to only users with keys. For example, 31 // you could choose to allow anyone with a DNS key on your server to 42 // You could use a single key which you give to all authorized users, bu [all...] |
/external/valgrind/none/tests/s390x/ |
op_exception.stderr.exp | 8 location. If you are running Memcheck and you just saw a 11 i.e. it's Valgrind's fault. If you think this is the case or 12 you are not sure, please let us know and we'll try to fix it. 21 location. If you are running Memcheck and you just saw a 24 i.e. it's Valgrind's fault. If you think this is the case or 25 you are not sure, please let us know and we'll try to fix it. 34 location. If you are running Memcheck and you just saw [all...] |
/ndk/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/prebuilts/ndk/current/sources/cxx-stl/stlport/stlport/stl/ |
_ioserr.h | 9 # error STLport iostreams header cannot be used; you chose not to use iostreams in the STLport configuration file (stlport/stl/config/user_config.h).
|
/toolchain/binutils/binutils-2.25/ld/testsuite/ld-elf/ |
orphan.d | 6 # if not using elf32.em, you don't get fancy orphan handling
|
pr349.d | 7 # if not using elf32.em, you don't get fancy section handling
|
/external/valgrind/memcheck/tests/ |
supp_unknown.stderr.exp | 6 If you believe this happened as a result of a stack 8 possible), you can try to increase the size of the
|
/external/valgrind/none/tests/amd64-linux/ |
bug345887.stderr.exp | 5 If you believe this happened as a result of a stack 7 possible), you can try to increase the size of the
|
/external/valgrind/none/tests/amd64-solaris/ |
coredump_single_thread.stderr.exp | 5 If you believe this happened as a result of a stack 7 possible), you can try to increase the size of the
|
coredump_single_thread_sse.stderr.exp | 7 If you believe this happened as a result of a stack 9 possible), you can try to increase the size of the
|
/external/valgrind/none/tests/linux/ |
blockfault.stderr.exp | 6 If you believe this happened as a result of a stack 8 possible), you can try to increase the size of the
|
stack-overflow.stderr.exp | 8 If you believe this happened as a result of a stack 10 possible), you can try to increase the size of the
|
/external/valgrind/none/tests/solaris/ |
block_all_signals.stderr.exp | 6 If you believe this happened as a result of a stack 8 possible), you can try to increase the size of the
|
blockfault.stderr.exp | 6 If you believe this happened as a result of a stack 8 possible), you can try to increase the size of the
|