Home
last modified time | relevance | path

Searched refs:machine (Results 1 – 25 of 70) sorted by relevance

123

/frameworks/ml/bordeaux/learning/multiclass_pa/native/
Dutil.cpp35 MulticlassPA* machine = NULL; in CreateMulticlassPA() local
37 machine = reinterpret_cast<MulticlassPA*>( in CreateMulticlassPA()
40 machine = reinterpret_cast<MulticlassPA*>( in CreateMulticlassPA()
43 machine = new MulticlassPA(num_classes, num_dimensions, aggressiveness); in CreateMulticlassPA()
45 machine = reinterpret_cast<MulticlassPA*>( in CreateMulticlassPA()
50 return machine; in CreateMulticlassPA()
/frameworks/compile/mclinker/lib/Target/X86/
DX86GNUInfo.h21 uint32_t machine() const { return llvm::ELF::EM_386; } in machine() function
34 uint32_t machine() const { return llvm::ELF::EM_X86_64; } in machine() function
DX86LDBackend.h37 uint32_t machine() const;
/frameworks/base/docs/html/ndk/guides/
Dx86-64.jd22 <p>To generate 64-bit machine code for x86, add {@code x86_64} to the {@code APP_ABI} definition in
33 {@code $PROJECT/libs/x86_64/} on your host machine, where {@code $PROJECT} is the root directory
49 <p>The NDK provides native versions of Android APIs for 64-bit x86 machine code starting from
Dabis.jd18 <i>ABI</i>. The ABI defines, with great precision, how an application's machine code is supposed to
25 <li>The CPU instruction set(s) that the machine code should use.</li>
32 <li>The list of function symbols available to your machine code at runtime,
191 machine code for NEON, see
354 <p>By default, the NDK generates machine code for the armeabi ABI. You can
355 generate ARMv7-a-compatible machine code, instead, by adding the following line
361 <p>To build machine code for two or more distinct ABIs, using spaces as delimiters. For
368 <p>This setting tells the NDK to build two versions of your machine code: one
373 <p>When you build multiple machine-code versions, the build system copies the libraries to your
376 is larger than one containing only the machine code for a single system; the tradeoff is
[all …]
Dndk-gdb.jd17 session for your NDK-generated machine code.</p>
53 find various system libraries. This is normal, because your host machine does not contain
146 running on different devices or emulators connected to the same host machine.</p></td>
162 several devices or emulators connected to your host machine. Their meanings are as follows:</p>
Dmips.jd19 <p>To generate MIPS machine code, include {@code mips} in your
/frameworks/compile/mclinker/lib/Target/AArch64/
DAArch64GNUInfo.h21 uint32_t machine() const { return llvm::ELF::EM_AARCH64; } in machine() function
/frameworks/compile/mclinker/lib/Target/ARM/
DARMGNUInfo.h21 uint32_t machine() const { return llvm::ELF::EM_ARM; } in machine() function
/frameworks/compile/mclinker/lib/Target/Hexagon/
DHexagonGNUInfo.h25 uint32_t machine() const { return llvm::ELF::EM_HEXAGON; } in machine() function
DHexagonLDBackend.h37 uint32_t machine() const;
/frameworks/base/docs/html/training/efficient-downloads/
Defficient-network-access.jd16 <li><a href="#RadioStateMachine">Understand the radio state machine</a></li>
17 <li><a href="#AppsStateMachine">Understand how apps can impact the radio state machine</a></li>
34 <p>This lesson introduces the wireless radio state machine and explains how your app's connectivity…
40 <p>The state machine for a typical 3G network radio consists of three energy states:
48 <p>To minimize latency, the state machine uses a delay to postpone the transition to lower energy s…
51 <p class="img-caption"><strong>Figure 1.</strong> Typical 3G wireless radio state machine.</p>
53 <p>The radio state machine on each device, particularly the associated transition delay ("tail time…
55 <p>This lesson describes a representative state machine for a typical 3G wireless radio, based on <…
63 …tions to the full power state. In the case of the typical 3G radio state machine described above, …
84 …nd the likelihood of it being used. As a rough guide, based on the state machine described above, …
Dindex.jd39 …<dd>This lesson introduces the wireless radio state machine, explains how your app’s connectivity …
42 …best mitigate the effect of background updates on the underlying wireless radio state machine.</dd>
/frameworks/compile/mclinker/lib/Target/Mips/
DMipsGNUInfo.h24 uint32_t machine() const;
DMipsGNUInfo.cpp28 uint32_t MipsGNUInfo::machine() const { in machine() function in mcld::MipsGNUInfo
/frameworks/compile/mclinker/include/mcld/Target/
DGNUInfo.h29 virtual uint32_t machine() const = 0;
/frameworks/base/docs/html/training/auto/testing/
Dindex.jd31 <p>The Desktop Head Unit (DHU) enables your development machine to emulate an
43 machine for testing your apps. Once you’ve
48 <p>Follow these steps to install the DHU on your development machine:</p>
99 <p>Run the DHU by connecting your mobile device to a development machine and
116 <li>Connect the mobile device to the development machine via USB.</li>
120 <li>On the development machine, run the following {@code adb} command to
122 development machine's port 5277 to the same port number on the Android device.
169 <strong>Figure 4.</strong> DHU launches on the development machine.
507 Desktop Head Unit, which enables your development machine to act as if it were an Android Auto head
/frameworks/compile/mclinker/lib/Support/Windows/
DFileSystem.inc36 // FIXME: the extension depends on target machine, not host machine.
/frameworks/base/docs/html/training/wearables/apps/
Dbt-debugging.jd25 handheld device that's connected to your development machine.</p>
61 <li>Connect the handheld to your machine over USB and run:
Dcreating.jd92 <li>Connect the handheld to your machine through USB.</li>
121 <li>Connect the wearable to your machine through USB, so you can install apps directly to it
126 to your machine via USB, you can try
/frameworks/base/docs/html/training/testing/unit-testing/
Dindex.jd44 <li><strong>Local tests:</strong> Unit tests that run on your local machine only. These tests are
60 <dd>Learn how to build unit tests that run on your local machine.</dd>
/frameworks/compile/mclinker/include/mcld/LD/
DDiagCommonKinds.inc21 "target machine (%1) is incompatible.",
23 "target machine (%1) is incompatible.")
/frameworks/opt/net/wifi/tests/wifitests/
DREADME.md44 similar to runtest. If you have multiple devices connected to your machine make sure to set the
/frameworks/compile/libbcc/
DREADME.rst26 into machine code
142 magic word, version, machine integer type information (the endianness,
/frameworks/compile/libbcc/tests/debuginfo/
DREADME7 build machine (currently, only Linux has been tested extensively) and target

123