| /external/llvm/lib/Target/X86/MCTargetDesc/ |
| X86MachObjectWriter.cpp | 133 // FIXME: I believe this is broken, I don't think the linker can understand
134 // it. I think it would require a local relocation, but I'm not sure if that
|
| /external/mesa3d/src/gallium/drivers/r600/ |
| r600_blit.c | 217 * I don't think this case occurs often though. */
296 * I don't think this case occurs often though. */
|
| /external/netperf/ |
| netcpu_looper.c | 204 /* processors. I *think* this is the most reasonable thing to */
447 /* will go away too, so I don't think I need any explicit thread */
|
| /external/skia/src/animator/ |
| SkAnimator.cpp | 545 //i think we can handle the case where the displayable itself is an array differently from the
546 //case where it has an array - for one thing, if it is an array, i think we can change its type
|
| /external/strace/ |
| strace.1 | 399 can think of this as an abbreviation for
638 It is instructive to think about system call inputs and outputs
|
| /external/valgrind/coregrind/m_syswrap/ |
| syswrap-amd64-darwin.c | 537 wasteful but I don't think is harmful. A better solution
579 DDD: I think this is plain wrong .. if we get to
|
| syswrap-x86-darwin.c | 485 wasteful but I don't think is harmful. A better solution
527 DDD: I think this is plain wrong .. if we get to
|
| /frameworks/base/core/java/android/view/inputmethod/ |
| EditorInfo.java | 108 * By default, IMEs may go into full screen mode when they think
164 * user. Setting this generally means that you think that in fullscreen mode,
|
| /frameworks/base/docs/html/design/wear/ |
| watchfaces.jd | 263 overlaying a time-based watch face with extra data. Rather, think about how the data can
311 possible: Neither you nor the user should think of watch faces as full-fledged apps. Figure 1
|
| /frameworks/base/docs/html/training/articles/ |
| perf-tips.jd | 324 performed in software—something to think about if you're designing a
413 not measuring what you think you're measuring (because, say, the VM has
|
| smp.jd | 682 you can?t think about consistency issues in terms of instruction execution.
683 Always think in terms of memory accesses.)</p>
727 think of them as a ?flush? call that causes a series of actions to happen.
728 Instead, think of them as a dividing line in time for operations on the current
[all...] |
| /prebuilts/ndk/5/sources/cxx-stl/gnu-libstdc++/include/bits/ |
| stl_iterator.h | 410 * container (you can think of the position as being permanently at
493 * container (you can think of the position as being permanently at
[all...] |
| /prebuilts/ndk/6/sources/cxx-stl/gnu-libstdc++/include/bits/ |
| stl_iterator.h | 410 * container (you can think of the position as being permanently at
493 * container (you can think of the position as being permanently at
[all...] |
| /prebuilts/ndk/7/sources/cxx-stl/gnu-libstdc++/include/bits/ |
| stl_iterator.h | 410 * container (you can think of the position as being permanently at
493 * container (you can think of the position as being permanently at
[all...] |
| /prebuilts/ndk/8/sources/cxx-stl/gnu-libstdc++/4.4.3/include/bits/ |
| stl_iterator.h | 410 * container (you can think of the position as being permanently at
493 * container (you can think of the position as being permanently at
[all...] |
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/compiler/ |
| pyassem.py | 30 # XXX think we need to specify when there is implicit transfer
35 # I think this strategy works: each block has a child
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/distutils/ |
| cmd.py | 16 of the Distutils. A useful analogy for command classes is to think of
77 # backwards compatibility (I think)?
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/compiler/ |
| pyassem.py | 30 # XXX think we need to specify when there is implicit transfer
35 # I think this strategy works: each block has a child
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/distutils/ |
| cmd.py | 16 of the Distutils. A useful analogy for command classes is to think of
77 # backwards compatibility (I think)?
|
| /system/keymaster/ |
| authorization_set_test.cpp | 274 // broken serialized data and I can't think of a better way to write this.
291 // Check that stuff is where we think.
|
| /external/valgrind/helgrind/ |
| hg_intercepts.c | 590 this matter? Not sure, but I don't think so. */
634 this matter? Not sure, but I don't think so. */
676 this matter? Not sure, but I don't think so. */
[all...] |
| /external/libvpx/libvpx/vp8/common/ppc/ |
| loopfilter_filters_altivec.asm | 32 ;# when we think of them as permutations of address bits: Concatenate a
33 ;# group of vector registers and think of it as occupying a block of
180 ;# defined above. We think of both groups of 4 registers as having
[all...] |
| /external/littlemock/src/com/google/testing/littlemock/ |
| LittleMock.java | 99 * that don't work in the same way as Mockito's implementation. Where that is the case I think we
521 * and I can't think of an elegant way of doing it, and in any case I really like the current
[all...] |
| /external/valgrind/include/vki/ |
| vki-arm64-linux.h | 167 __vki_sigrestore_t sa_restorer; // I don't think arm64 has this
500 /* I think that the new name in the kernel for these is "user_pt_regs"
560 //ZZ // I think this LDT stuff will have to be reinstated for amd64, but I'm not
|
| /hardware/intel/common/omx-components/videocodec/libvpx_internal/libvpx/vp8/common/ppc/ |
| loopfilter_filters_altivec.asm | 32 ;# when we think of them as permutations of address bits: Concatenate a
33 ;# group of vector registers and think of it as occupying a block of
180 ;# defined above. We think of both groups of 4 registers as having
[all...] |
