| /frameworks/native/include/cpustats/ |
| D | README.txt | 1 This is a static library of CPU usage statistics, originally written
5 * should be related to CPU usage statistics
|
| /frameworks/compile/slang/ |
| D | slang.cpp | 174 void Slang::createTarget(const std::string &Triple, const std::string &CPU, in createTarget() argument
181 if (!CPU.empty()) in createTarget()
182 mTargetOpts.CPU = CPU; in createTarget()
260 void Slang::init(const std::string &Triple, const std::string &CPU, in init() argument
273 createTarget(Triple, CPU, Features); in init()
|
| D | slang.h | 94 void createTarget(std::string const &Triple, std::string const &CPU,
171 void init(const std::string &Triple, const std::string &CPU,
|
| D | slang_backend.cpp | 157 if (mTargetOpts.CPU.size() || mTargetOpts.Features.size()) { in CreateCodeGenPasses()
170 TargetInfo->createTargetMachine(Triple, mTargetOpts.CPU, FeaturesStr, in CreateCodeGenPasses()
|
| /frameworks/base/docs/html/tools/debugging/ |
| D | debugging-devtools.jd | 60 <dt><strong>Show CPU usage</strong></dt>
62 <dd>Displays CPU meters at the top of the screen, showing how much the CPU is being used. The
63 top red bar shows overall CPU usage, and the green bar underneath it shows the CPU time spent
|
| D | index.jd | 109 that provide useful information such as CPU usage and frame rate. You can also transfer the
127 <dd>The device can display useful information such as CPU usage or highlights
|
| /frameworks/base/docs/html/tools/sdk/ndk/ |
| D | overview.jd | 52 <li>ARMv5TE, including Thumb-1 instructions (see {@code docs/CPU-ARCH-ABIS.html} for more
56 NEON/VFPv3-D32 instructions (see {@code docs/CPU-ARM-NEON.html} for more information)</li>
58 <li>x86 instructions (see {@code docs/CPU-X86.html} for more information)</li>
60 <li>MIPS instructions (see {@code docs/CPU-MIPS.html} for more information)</li>
64 devices such as the Verizon Droid or Google Nexus One that have a compatible CPU. The main
70 Complete information is provided in the CPU-ARCH-ABIS.HTML in the NDK package.</p>
83 <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't
147 having to handle the toolchain/platform/CPU/ABI details. You create very short build files to
177 <li>CPU-ARCH-ABIS.HTML — a description of supported CPU architectures and how to target
180 <li>CPU-FEATURES.HTML — a description of the <code>cpufeatures</code> static library that
[all …]
|
| D | index.jd | 57 <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't
131 MIPS support, see {@code docs/CPU-MIPS.html} in the NDK package.
156 is compiled for the device's CPU architecture.</p>
327 x86 CPU features ({@code SSSE3}, {@code MOVBE} and {@code POPCNT}). See
328 {@code docs/CPU-FEATURES.html} for more details.</li>
705 see <code>docs/CPU-X86.html</code> in the NDK package.
935 …of the CPU type (some devices previously reported ARMv7 CPU when the device really was an ARMv6). …
983 <li>Adds a new Android-specific ABI for ARM-based CPU architectures,
985 include these CPU instruction set extensions:
999 app detect the host device's CPU features at runtime. Specifically, applications can
[all …]
|
| /frameworks/av/media/libstagefright/codecs/on2/h264dec/source/arm11_asm/ |
| D | win_asm.bat | 2 set ASMFLAGS= -checkreglist -CPU ARM1136 -PreDefine "H264DEC_WINASM SETL {TRUE}"
|
| /frameworks/compile/libbcc/lib/ExecutionEngine/ |
| D | Compiler.h | 69 static std::string CPU; variable
|
| D | Compiler.cpp | 112 std::string Compiler::CPU; member in bcc::Compiler
309 if (!CPU.empty() || !Features.empty() || !ExtraFeatures.empty()) { in compile()
326 TM = Target->createTargetMachine(Triple, CPU, FeaturesStr, in compile()
|
| /frameworks/base/docs/html/guide/topics/renderscript/ |
| D | compute.jd | 36 It also supports different types of processors such as the CPU, GPU or DSP. Renderscript
91 …processor (CPU, GPU, and DSP for instance) architectures. It supports all of these architectures w…
107 …on processors other than the main CPU (such as the GPU), so if this occurs, debugging becomes more…
121 For now, Renderscript can only take advantage of CPU
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | pausing.jd | 74 <li>Stop animations or other ongoing actions that could consume CPU.</li>
103 However, you should avoid performing CPU-intensive work during {@link
|
| D | stopping.jd | 88 to perform larger, more CPU intensive shut-down operations, such as writing information to a
|
| /frameworks/base/docs/html/intl/ja/guide/developing/ |
| D | other-ide.jd | 264 <p>このセクションでは、画面上でのデバッグ情報（CPU の使用率など）の表示方法や、総合開発環境に接続してエミュレータ上で実行するアプリケーションをデバッグする方法について説明します。 </p>
269 …す</strong>。設定には、デバッガ接続まで Activity のアプリケーション起動をブロックするオプションなどが含まれます。エミュレータでの CPU 使用率や画面の更新率の表示のように、こ…
|
| /frameworks/base/docs/html/tools/ |
| D | index.jd | 70 <li>Built-in memory analysis, performance/CPU profiling, OpenGL ES tracing.</li>
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.3-highlights.jd | 120 the device awake for too long or that are consuming CPU while running in the
217 events faster and more efficiently, minimizing CPU utilization during event
220 or other CPU-intensive operations. </li>
|
| D | android-2.2-highlights.jd | 173 <p><span class="green">Dalvik Performance Boost:</span> 2x-5x performance speedup for CPU-heavy code
|
| /frameworks/base/docs/html/tools/devices/ |
| D | emulator.jd | 125 <li>An ARMv5 CPU and the corresponding memory-management unit (MMU)</li>
316 this type of acceleration, you should first determine if your development system’s CPU supports one
324 <p>The specifications from the manufacturer of your CPU should indicate if it supports
325 virtualization extensions. If your CPU does not support one of these virtualization technologies,
332 <p>Once you have determined that your CPU supports virtualization extensions, make sure you can work
370 <strong>CPU/ABI</strong> field. You may need to select a specific <strong>Target</strong> value, or
371 select a <strong>Target</strong> value and then select a specific <strong>CPU/ABI</strong>
380 Accelerated Execution Manager (Intel HAXM). The software requires an Intel CPU with
441 Execution Manager (Intel HAXM) kernel extension to allow the Android emulator to make use of CPU
|
| /frameworks/base/docs/html/training/graphics/opengl/ |
| D | draw.jd | 120 in terms of CPU cycles and processing time, so you should avoid doing this more than once. If you do
|
| /frameworks/native/opengl/specs/ |
| D | EGL_ANDROID_blob_cache.txt | 38 programming for a long time. It can consume seconds of CPU cycles during
|
| /frameworks/base/docs/html/training/displaying-bitmaps/ |
| D | process-bitmap.jd | 46 size of image, power of CPU, etc.). If one of these tasks blocks the UI thread, the system flags
|
| /frameworks/compile/mclinker/ |
| D | INSTALL | 153 CPU-COMPANY-SYSTEM
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | mediaplayer.jd | 352 not necessary, including the CPU and the WiFi hardware.
365 <p>To ensure that the CPU continues running while your {@link android.media.MediaPlayer} is
377 <p>However, the wake lock acquired in this example guarantees only that the CPU remains awake. If
|
| /frameworks/base/tests/FrameworkPerf/src/com/android/frameworkperf/ |
| D | TestService.java | 220 CPU, enumConstant
|