Searched refs:looks (Results 1 – 25 of 332) sorted by relevance
12345678910>>...14
| /external/llvm/test/Transforms/ScalarRepl/ |
| D | phinodepromote.ll | 5 ; often generates code that looks like this (when it codegen's ?: exprs as
8 ; This testcase is what the following program looks like when it reaches
|
| /external/eigen/doc/ |
| D | ClassHierarchy.dox | 66 … bad idea). \c %EigenBase is really the absolute base class for anything that remotely looks like a
74 The inheritance diagram for Matrix looks as follows:
85 The inheritance diagram for Array looks as follows:
96 …eritance diagram for some other matrix expression class, here denoted by \c SomeMatrixXpr, looks as
107 …nheritance diagram for some other array expression class, here denoted by \c SomeArrayXpr, looks as
|
| /external/llvm/test/CodeGen/X86/ |
| D | combine-multiplies.ll | 3 ; Source file looks something like this:
22 ; Output looks roughly like this:
58 ; Source looks something like this:
70 ; Output looks something like this:
|
| /external/icu/icu4j/main/classes/core/src/com/ibm/icu/ |
| D | ICUConfig.properties | 33 # File system path where ICU looks for binary data files.
34 # If not empty, then ICU looks for binary data files before looking for data on the classpath.
|
| /external/icu/android_icu4j/resources/android/icu/ |
| D | ICUConfig.properties | 33 # File system path where ICU looks for binary data files.
34 # If not empty, then ICU looks for binary data files before looking for data on the classpath.
|
| /external/llvm/test/Assembler/ |
| D | 2002-05-02-InvalidForwardRef.ll | 3 ; It looks like the assembler is not forward resolving the function declaraion
|
| /external/e2fsprogs/tests/f_invalid_bad_inode/ |
| D | expect.1 | 2 The bad block inode looks invalid. Clear? yes
|
| /external/llvm/test/MC/AsmParser/ |
| D | undefined-local-symbol.s | 4 # of what an assembler local symbol looks like (i.e., 'L' prefix.)
|
| /external/e2fsprogs/tests/f_dir_bad_mode/ |
| D | expect.1 | 2 Inode 12 is a socket but it looks like it is really a directory.
|
| /external/autotest/server/control_segments/ |
| D | provision | 40 # The scheduler only looks at the return code of autoserv to see if
58 # If we finish successfully, nothing in autotest ever looks at the
|
| /external/llvm/test/CodeGen/AArch64/ |
| D | arm64-simplest-elf.ll | 8 ; Check source looks ELF-like: no leading underscore, comments with //
|
| D | atomic-ops-not-barriers.ll | 21 ; with isBarrier. For now, look for something that looks like "somewhere".
|
| /external/skia/site/dev/sheriffing/ |
| D | trooper.md | 94 - Machine name ends with "a3" or "a4" -> ssh command looks like `ssh
96 - Machine name ends with "m3" -> ssh command looks like `ssh build5-m3.golo`
100 - To access bots in the Chrome infra GCE -> command looks like `gcutil
|
| /external/clang/test/CodeGenObjC/ |
| D | instance-method-metadata.m | 7 /** The problem looks like clang getting confused when a single translation unit
|
| /external/llvm/test/Integer/ |
| D | basictest_bt.ll | 7 ; format looks anyways (except for negative vs positive offsets)...
|
| /external/llvm/test/Feature/ |
| D | basictest.ll | 6 ; format looks anyways (except for negative vs positive offsets)...
|
| /external/autotest/client/site_tests/ui_SystemTray/ |
| D | control.guest.link | 21 data that helps us understand how system tray looks in the lab for purposes of
|
| D | control.link | 21 data that helps us understand how system tray looks in the lab for purposes of
|
| /external/skia/src/animator/ |
| D | thingstodo.txt | 11 looks like random takes a parameter when it should take zero parameters
|
| /external/autotest/client/site_tests/ui_SettingsPage/ |
| D | control.link | 21 looks over multiple builds before writing image comparison based tests.
|
| /external/llvm/test/CodeGen/AMDGPU/ |
| D | lds-output-queue.ll | 47 ; The instruction selection phase will generate ISA that looks like this:
67 ; final program which looks like this:
|
| /external/jemalloc/android/scripts/ |
| D | README | 21 In the code that looks similar to this:
|
| /external/opencv3/doc/py_tutorials/py_feature2d/py_features_meaning/ |
| D | py_features_meaning.markdown | 61 patch, it looks the same. For black patch, it is an edge. If you move it in vertical direction (i.e.
62 along the gradient) it changes. Put along the edge (parallel to edge), it looks the same. And for
63 red patch, it is a corner. Wherever you move the patch, it looks different, means it is unique. So
|
| /external/iproute2/examples/ |
| D | README.cbq | 39 # So, filename looks like:
44 # | |___________________ ID (0000-FFFF), let ID looks like shaper's rate
|
| /external/llvm/test/CodeGen/ARM/ |
| D | 2012-03-26-FoldImmBug.ll | 3 ; ARM has a peephole optimization which looks for a def / use pair. The def
|
12345678910>>...14