| /bionic/libc/arch-arm/generic/bionic/ |
| strcmp.S | 116 * interesting byte is at the other end of the word, but the
119 * little-endian case we can't just shift the interesting bits up.
|
| /dalvik/vm/analysis/ |
| CodeVerify.h | 126 * During verification, we associate one of these with every "interesting"
193 * entries for code units that hold the start of an "interesting"
|
| /device/samsung/manta/ |
| media_codecs.xml | 37 <MediaCodec name="OMX.foo.bar" type="something/interesting" />
43 <Type name="something/interesting" />
|
| /external/chromium/net/tools/flip_server/ |
| balsa_visitor_interface.h | 17 // which does absolutely nothing. If you'd prefer to have interesting
172 // with the BytesSpliced() function, but in the future other interesting
|
| /external/chromium_org/net/tools/flip_server/ |
| balsa_visitor_interface.h | 16 // which does absolutely nothing. If you'd prefer to have interesting
171 // with the BytesSpliced() function, but in the future other interesting
|
| /external/clang/docs/ |
| LibASTMatchers.rst | 5 This document explains how to use Clang's LibASTMatchers to match interesting
76 Matcher expressions allow you to specify which parts of the AST are interesting
|
| RAVFrontendAction.rst | 88 of the Clang AST to drill through to the parts that are interesting for
120 do more interesting things with AST nodes, like looking up their source
|
| /external/clang/test/CodeGenCXX/ |
| debug-info-template.cpp | 58 // The interesting null pointer: -1 for member data pointers (since they are
73 char pad[8]; // make the member pointer to 'e' a bit more interesting (nonzero)
|
| /frameworks/base/docs/html/training/sharing/ |
| receive.jd | 36 be interested in receiving text content, like an interesting web URL, from another app. The
147 be more complicated like applying an interesting photo filter to an image. It's really specific
|
| /libcore/luni/src/test/java/libcore/java/util/ |
| FormatterTest.java | 72 // The interesting case is -123, where you might naively output "-,123" if you're just
74 // before the first separator may also be interesting.
|
| /external/llvm/docs/tutorial/ |
| LangImpl2.rst | 204 There are some interesting aspects to this. The most important one is
225 This function illustrates a number of interesting things about the
235 2) Another interesting aspect of this function is that it uses recursion
286 also has recursion and error handling. One interesting aspect of this is
537 straight-forward and not very interesting (once you've survived
618 top-level dispatch loop. There isn't much interesting here, so I'll just
638 The most interesting part of this is that we ignore top-level
|
| LangImpl1.rst | 72 variables along with an assignment operator. The interesting part
88 interesting "hello world" tutorials, I think the breadth of this
140 A more interesting example is included in Chapter 6 where we write a
|
| OCamlLangImpl1.rst | 72 local variables along with an assignment operator. The interesting
88 interesting "hello world" tutorials, I think the breadth of this
140 A more interesting example is included in Chapter 6 where we write a
|
| /frameworks/base/core/java/com/android/internal/os/ |
| ProcessCpuTracker.java | 188 public boolean interesting; field in class:ProcessCpuTracker.Stats
373 if (st.interesting) {
454 st.interesting = true;
478 } else if (st.interesting) {
492 if (!first && st.interesting) {
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/ |
| HTMLParser.py | 103 self.interesting = interesting_normal
131 self.interesting = re.compile(r'</\s*%s\s*>' % self.cdata_elem, re.I)
134 self.interesting = interesting_normal
145 match = self.interesting.search(rawdata, i) # < or &
224 assert 0, "interesting.search() lied"
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/ |
| HTMLParser.py | 103 self.interesting = interesting_normal
131 self.interesting = re.compile(r'</\s*%s\s*>' % self.cdata_elem, re.I)
134 self.interesting = interesting_normal
145 match = self.interesting.search(rawdata, i) # < or &
224 assert 0, "interesting.search() lied"
|
| /development/samples/ApiDemos/src/com/example/android/apis/app/ |
| LoaderCustom.java | 160 * Helper for determining if the configuration has changed in an interesting
180 * Helper class to look for interesting changes to the installed apps
301 // Has something interesting in the configuration changed since we
|
| /development/samples/Support4Demos/src/com/example/android/supportv4/app/ |
| LoaderCustomSupport.java | 162 * Helper for determining if the configuration has changed in an interesting
182 * Helper class to look for interesting changes to the installed apps
303 // Has something interesting in the configuration changed since we
|
| /external/clang/lib/Serialization/ |
| GlobalModuleIndex.cpp | 369 /// consider this identifier to be interesting.
372 /// \brief A mapping from all interesting identifiers to the set of module
373 /// files in which those identifiers are considered interesting.
452 /// \brief The identifier and whether it is "interesting".
458 // The first bit indicates whether this identifier is interesting.
513 // Handle potentially-interesting records below.
|
| /docs/source.android.com/src/source/ |
| developing.jd | 28 <p><strong>Git</strong> is an open-source version-control system designed to handle very large projects that are distributed over multiple repositories. In the context of Android, we use Git for local operations such as local branching, commits, diffs, and edits. One of the challenges in setting up the Android project was figuring out how to best support the outside community--from the hobbiest community to large OEMs building mass-market consumer devices. We wanted components to be replaceable, and we wanted interesting components to be able to grow a life of their own outside of Android. We first chose a distributed revision control system, then further narrowed it down to Git.</p>
75 <p>Start a topic branch in your local work environment whenever you begin a change, for example when you begin work on a bug or new feature. A topic branch is not a copy of the original files; it is a pointer to a particular commit. This makes creating local branches and switching among them a light-weight operation. By using branches, you can isolate one aspect of your work from the others. For an interesting article about using topic branches, see <a href="http://www.kernel.org/pub/software/scm/git/docs/howto/separating-topic-branches.txt">Separating topic branches</a>.
|
| /external/chromium_org/chrome/common/extensions/docs/templates/articles/ |
| sandboxingEval.html | 92 In order to do something interesting with the sandboxed file, we need to load
179 interesting with the <code>html</code> data we've been passed. In this case,
|
| /external/chromium_org/chrome/utility/media_galleries/ |
| itunes_library_parser_unittest.cc | 175 // In the body of a track dictionary before the interesting entries.
183 // In the body of a track dictionary after the interesting entries.
|
| /external/chromium_org/content/public/android/java/src/org/chromium/content/common/ |
| PerfTraceEvent.java | 185 * time delta between begin and end is usually interesting to
225 * memory usage delta between begin and end is usually interesting to
|
| /external/chromium_org/third_party/angle_dx11/src/compiler/ |
| PoolAlloc.h | 209 int numCalls; // just an interesting statistic
210 size_t totalBytes; // just an interesting statistic
|
| /external/llvm/docs/HistoricalNotes/ |
| 2007-OriginalClangReadme.txt | 82 In the future I hope this toolkit will grow to include new and interesting
135 highlight regions of interesting code (e.g. the LHS and RHS of a binop).
|
