| /frameworks/base/core/java/android/text/method/ |
| ScrollingMovementMethod.java | 39 protected boolean up(TextView widget, Spannable buffer) { method in class:ScrollingMovementMethod
|
| /prebuilts/devtools/tools/ |
| ddms.bat | 19 rem Set up prog to be the path of this script, including following symlinks,
20 rem and set up progdir to be the fully-qualified pathname of its directory.
|
| hierarchyviewer.bat | 19 rem Set up prog to be the path of this script, including following symlinks,
20 rem and set up progdir to be the fully-qualified pathname of its directory.
|
| /bionic/libdl/ |
| Android.mk | 32 # against libc creating a circular dependency which is removed and we end up
|
| /cts/tests/tests/text/src/android/text/method/cts/ |
| ScrollingMovementMethodTest.java | 541 mResult = method.up(mTextView, mSpannable);
548 mResult = method.up(mTextView, mSpannable);
555 mResult = method.up(mTextView, mSpannable);
563 method.up(null, mSpannable);
569 method.up(mTextView, null);
598 new MyScrollingMovementMethod().up(mTextView, mSpannable);
[all...] |
| /dalvik/vm/compiler/template/armv5te/ |
| TEMPLATE_INVOKE_METHOD_NO_OPT.S | 26 @ set up newSaveArea
|
| /dalvik/vm/mterp/armv5te/ |
| OP_CHECK_CAST.S | 68 b .L${opcode}_resolved @ pick up where we left off
|
| OP_IPUT.S | 26 bne .L${opcode}_finish @ yes, finish up
|
| OP_IPUT_OBJECT.S | 26 bne .L${opcode}_finish @ yes, finish up
|
| OP_IPUT_WIDE.S | 21 bne .L${opcode}_finish @ yes, finish up
|
| /dalvik/vm/mterp/armv6t2/ |
| OP_IPUT_WIDE.S | 20 bne .L${opcode}_finish @ yes, finish up
|
| /dalvik/vm/mterp/mips/ |
| OP_CHECK_CAST.S | 71 b .L${opcode}_resolved # pick up where we left off
|
| OP_INSTANCE_OF.S | 81 b .L${opcode}_resolved # pick up where we left off
|
| OP_IPUT_OBJECT.S | 27 bnez v0, .L${opcode}_finish # yes, finish up
|
| OP_IPUT_WIDE.S | 22 bnez v0, .L${opcode}_finish # yes, finish up
|
| /dalvik/vm/mterp/x86/ |
| OP_CHECK_CAST.S | 77 jmp .L${opcode}_resolved # pick up where we left off
|
| /device/lge/mako/camera/QCamera/HAL/core/ |
| Android.mk | 71 # if debug service layer and up , use stub camera!
|
| /device/ti/panda/wl12xx/ |
| Android.mk | 86 # Clean up tmp vars
|
| /external/antlr/antlr-3.4/runtime/ObjC/ANTLR.framework/Headers/ |
| ANTLRBufferedTreeNodeStream.h | 63 id<ANTLRTree> up; variable
84 @property (retain, getter=getUp, setter=setUp:) id<ANTLRTree> up; variable
|
| /external/antlr/antlr-3.4/runtime/ObjC/ANTLR.framework/Versions/A/Headers/ |
| ANTLRBufferedTreeNodeStream.h | 63 id<ANTLRTree> up; variable
84 @property (retain, getter=getUp, setter=setUp:) id<ANTLRTree> up; variable
|
| /external/antlr/antlr-3.4/runtime/ObjC/ANTLR.framework/Versions/Current/Headers/ |
| ANTLRBufferedTreeNodeStream.h | 63 id<ANTLRTree> up; variable
84 @property (retain, getter=getUp, setter=setUp:) id<ANTLRTree> up; variable
|
| /external/antlr/antlr-3.4/runtime/ObjC/Framework/ |
| ANTLRBufferedTreeNodeStream.h | 64 id up; variable
85 @property (retain, getter=getUp, setter=setUp:) id up; variable
|
| /external/ceres-solver/docs/ |
| faq.tex | 14 Most non-linear solvers we are aware of, define the problem and residuals in terms of scalars and it is possible to do this with Ceres also. However, it is our experience that in most problems small groups of scalars occur together. For example the three components of a translation vector and the four components of the quaternion that define the pose of a camera. Same is true for residuals, where it is common to have small vectors of residuals rather than just scalars. There are a number of advantages of using blocks. It saves on indexing information, which for large problems can be substantial. Blocks translate into contiguous storage in memory which is more cache friendly and last but not the least, it allows us to use SIMD/SSE based BLAS routines to significantly speed up various matrix operations.
45 Notice that out of the 20 cells, only 8 are non-zero, in fact out of the 288 entries only 48 entries are non-zero, thus we are hiding substantial sparsity from the solver, and using up much more memory. It is much better to break this up into 5 residual blocks. One residual block of size 2 that depends on all four parameter block and four residual blocks of size 4 each that depend on one parameter block at a time.
67 No. Ceres was designed from the grounds up to be a non-linear least squares solver. Currently we have no plans of extending it into a general purpose non-linear solver.
|
| /external/compiler-rt/lib/sanitizer_common/scripts/ |
| check_lint.sh | 18 (cd cpplint && svn up)
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.apache.ant_1.7.1.v20090120-1145/bin/ |
| antRun.bat | 34 rem of arguments (up to the command line limit, anyway).
|
