Home
last modified time | relevance | path

Searched refs:architectures (Results 1 – 13 of 13) sorted by relevance

/frameworks/compile/mclinker/include/mcld/Config/
DTargets.def.in10 |* This file enumerates all of the target architectures supported by *|
DTargets.def10 |* This file enumerates all of the target architectures supported by *|
/frameworks/base/tools/aapt/
DCommand.cpp1984 SortedVector<String8> architectures; in doDump() local
1986 architectures.add(ResTable::normalizeForOutput( in doDump()
2009 ssize_t index = architectures.indexOf(intel64); in doDump()
2011 index = architectures.indexOf(arm64); in doDump()
2015 printf("native-code: '%s'\n", architectures[index].string()); in doDump()
2016 architectures.removeAt(index); in doDump()
2021 const size_t archCount = architectures.size(); in doDump()
2028 printf(" '%s'", architectures[i].string()); in doDump()
/frameworks/base/docs/html/tools/
Dindex.jd114 … <li>Support for packaging multiple architectures in a single binary, for broad compatibility.</li>
/frameworks/base/docs/html/google/play/publishing/
Dmultiple-apks.jd40 <li><a href="#CpuArchOptions">Supporting multiple CPU architectures</a></li>
87 <li>Support different CPU architectures with each APK (such as for ARM, x86, and MIPS, when your
303 determined by the architectures you declare in the {@code Application.mk}
424 architectures, be aware that an APK for ARMv5TE will overlap with an APK for ARMv7. That is,
685 <h3 id="CpuArchOptions">Supporting multiple CPU architectures</h3>
687 <p>When using the Android NDK, you can create a single APK that supports multiple CPU architectures
688 by declaring each of the desired architectures with the {@code APP_ABI} variable in the
692 different CPU architectures:</p>
/frameworks/base/docs/html/about/versions/
Dandroid-3.0-highlights.jd158 <li><a href="#multicore">Support for multicore processor architectures</a></li>
230 <h3 id="multicore">Support for multicore processor architectures</h3>
232 … the platform designed to run on either single or multicore processor architectures. A variety of …
Dlollipop.jd108 …ime (JIT), and interpreted code. It’s supported on ARM, x86, and MIPS architectures and is fully 6…
112 <p>Android 5.0 introduces platform support for <strong>64-bit architectures</strong>&mdash;used by …
Djelly-bean.jd1204 a wider range of architectures:</p>
/frameworks/base/docs/html/about/
Dindex.jd53 multitude of device form-factors, chipset architectures, and price points. From
/frameworks/base/docs/html/tools/sdk/ndk/
Dindex.jd492 <li>Added the following functions to all architectures:
500 <li>Removed the following symbols from all architectures:
509 <li>Removed the following functions from the 64-bit architectures: <code>basename_r</code>,
511 <li>Removed the following function from the 32-bit architectures:
937 <li>Added <code>sys/cachectl.h</code> for all architectures. MIPS
2114 of the known architectures.
2320 architectures on Linux and Mac OS hosts. This support is disabled by default. Add {@code
2453 <li>Removed {@code if_dl.h} header from all platforms and architectures. The {@code
3360 <li>Adds a new Android-specific ABI for ARM-based CPU architectures,
3385 by the NDK. For example, you can build for both ARMv5 and ARMv7-A architectures at the
[all …]
/frameworks/base/docs/html/guide/topics/renderscript/
Dcompute.jd151 beneficial on some architectures due to additional optimizations only available with relaxed
/frameworks/base/docs/html/training/articles/
Dsmp.jd75 multiprocessor architectures. This document introduces issues that
94 hardware (for example, the radio). The CPUs may have different architectures, and the
513 <p>Because the architectures have different memory models, these barriers are
1802 <p>On some architectures, it’s possible to implement volatile stores with an
Dperf-jni.jd515 structures in integer fields in an object. To support architectures