| /external/compiler-rt/make/platform/ |
| multi_arch.mk | 2 architectures.
|
| darwin_fat.mk | 11 # UniversalArchs - A list of architectures to build for, when using universal build
14 # architectures should do so using distinct configs, with the
|
| clang_darwin.mk | 9 # A function that ensures we don't try to build for architectures that we
120 # If RC_SUPPORTED_ARCHS is defined, treat it as a list of the architectures we
|
| clang_linux.mk | 9 # We don't currently have any general purpose way to target architectures other
|
| clang_macho_embedded.mk | 9 # A function that ensures we don't try to build for architectures that we
|
| /external/chromium_org/third_party/yasm/source/patched-yasm/modules/objfmts/rdf/tests/ |
| rdtmain.asm | 12 ;; other 32 bit OS) systems (x86 architectures only!)
|
| /external/chromium_org/third_party/WebKit/Tools/Scripts/webkitpy/style/checkers/ |
| jsonchecker_unittest.py | 101 "platform": "mac-snowleopard", "configuration": "release", "architectures": ["x86_64"],
|
| /build/core/ |
| dex_preopt_libart_boot.mk | 8 # architectures on the device. The concrete architecture specific
|
| /frameworks/base/tools/aapt/ |
| Command.cpp | 1984 SortedVector<String8> architectures; local
[all...] |
| /external/chromium_org/native_client_sdk/src/doc/ |
| faq.rst | 46 architectures. Native Client also has experimental support for MIPS.
60 already supports all architectures NaCl does, and as PNaCl evolves it
122 * `Adapting Software Fault Isolation to Contemporary CPU Architectures
140 and/or more compatible across operating systems and architectures than
185 Openness, and Supported Architectures and Languages
201 What are the supported instruction set architectures?
206 with the x86-32, x86-64, and ARM instruction set architectures, as well
207 as experimental support for MIPS. As new architectures come along and
211 Native Client can currently execute on the same architectures as
214 cannot adapt to new architectures without recompilation, we therefor
[all...] |
| /external/libvorbis/doc/ |
| 02-bitpacking.tex | 21 In most contemporary architectures, a 'byte' is synonymous with an
32 The most ubiquitous architectures today consider a 'byte' to be an
|
| /development/ndk/tools/ |
| headers-diff-bionic-vs-ndk.py | 232 help = 'list of architectures\n(default: common arm x86 mips)')
|
| /bionic/libm/ |
| Android.mk | 295 # We'd really like to do this for all architectures, but since this wasn't done
|
| /bionic/libc/ |
| Android.mk | 855 # to avoid infinite recursion. For the other architectures we just build an
[all...] |
| /external/libunwind/doc/ |
| libunwind-dynamic.tex | 286 architectures, predicated or not).
313 certain architectures prefer the list of unwind directives to be
|
| libunwind.tex | 204 platforms (architectures). Indeed, a single program can use
|
| /external/chromium_org/native_client_sdk/src/tools/ |
| nacl_gcc.mk | 176 # Determine which architectures to build for. The user can set NACL_ARCH or
|
| /ndk/build/core/ |
| init.mk | 612 $(call ndk_log, This NDK supports the following target architectures and ABIS:)
|
| /external/pixman/ |
| configure | [all...] |
