/frameworks/ml/bordeaux/learning/multiclass_pa/native/ |
D | util.cpp | 35 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/ |
D | X86GNUInfo.h | 21 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
|
D | X86LDBackend.h | 37 uint32_t machine() const;
|
/frameworks/base/docs/html/ndk/guides/ |
D | x86-64.jd | 22 <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
|
D | abis.jd | 18 <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, 192 machine code for NEON, see 379 <p>By default, the NDK generates machine code for the armeabi ABI. You can 380 generate ARMv7-a-compatible machine code, instead, by adding the following line 386 <p>To build machine code for two or more distinct ABIs, using spaces as delimiters. For 393 <p>This setting tells the NDK to build two versions of your machine code: one 398 <p>When you build multiple machine-code versions, the build system copies the libraries to your 401 is larger than one containing only the machine code for a single system; the tradeoff is [all …]
|
D | ndk-gdb.jd | 17 session for your NDK-generated machine code.</p> 55 find various system libraries. This is normal, because your host machine does not contain 148 running on different devices or emulators connected to the same host machine.</p></td> 164 several devices or emulators connected to your host machine. Their meanings are as follows:</p>
|
D | mips.jd | 19 <p>To generate MIPS machine code, include {@code mips} in your
|
/frameworks/compile/mclinker/lib/Target/AArch64/ |
D | AArch64GNUInfo.h | 21 uint32_t machine() const { return llvm::ELF::EM_AARCH64; } in machine() function
|
/frameworks/compile/mclinker/lib/Target/ARM/ |
D | ARMGNUInfo.h | 21 uint32_t machine() const { return llvm::ELF::EM_ARM; } in machine() function
|
/frameworks/compile/mclinker/lib/Target/Hexagon/ |
D | HexagonGNUInfo.h | 25 uint32_t machine() const { return llvm::ELF::EM_HEXAGON; } in machine() function
|
D | HexagonLDBackend.h | 37 uint32_t machine() const;
|
/frameworks/compile/mclinker/lib/Target/Mips/ |
D | MipsGNUInfo.h | 24 uint32_t machine() const;
|
D | MipsGNUInfo.cpp | 28 uint32_t MipsGNUInfo::machine() const { in machine() function in mcld::MipsGNUInfo
|
/frameworks/compile/mclinker/include/mcld/Target/ |
D | GNUInfo.h | 29 virtual uint32_t machine() const = 0;
|
/frameworks/base/docs/html/training/efficient-downloads/ |
D | efficient-network-access.jd | 16 <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, …
|
D | index.jd | 39 …<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/base/docs/html/tools/help/ |
D | sqlite3.jd | 6 <p>From a remote shell to your device or from your host machine, you can use the <a href= 47 <li>Copy a database file from your device to your host machine:
|
/frameworks/base/docs/html/sdk/installing/ |
D | index.jd | 126 on a 64-bit machine. </p> 175 … download package is an executable file that starts an installer. The installer checks your machine 199 machine, such as a "Development" directory in your home directory.</p> 229 development machine, you might find these resources helpful: 238 machine, you need to install additional packages first. For Ubuntu 13.10 (Saucy Salamander) 337 // Show the proper instructions based on machine OS 356 /* Shows all the machine OS instructions */
|
/frameworks/base/docs/html/training/auto/start/ |
D | index.jd | 157 As you develop, you can run and test your app on your development machine 159 simulators and enables your development machine to simulate a vehicle 210 <p>Run the DHU by connecting your mobile device to a development machine and setting up a connectio… 224 <li>Connect the mobile device to the development machine via USB. Your device must be unlocked to 227 <li>On the development machine, run the following {@code adb} command to 229 development machine's port 5277 to the same port number on the Android device. 255 <strong>Figure 4.</strong> DHU launches on the development machine.
|
/frameworks/compile/mclinker/lib/Support/Windows/ |
D | FileSystem.inc | 36 // FIXME: the extension depends on target machine, not host machine.
|
/frameworks/base/docs/html/training/testing/unit-testing/ |
D | index.jd | 43 <li><strong>Local tests:</strong> Unit tests that run on your local machine only. These tests are 59 <dd>Learn how to build unit tests that run on your local machine.</dd>
|
/frameworks/base/docs/html/training/wearables/apps/ |
D | bt-debugging.jd | 25 handheld device that's connected to your development machine.</p> 61 <li>Connect the handheld to your machine over USB and run:
|
/frameworks/base/docs/html/tools/devices/ |
D | emulator.jd | 118 machine code to the OS and processor architecture of your development 119 machine.</p> 131 development machine)</li> 310 <p class="caution"><strong>Caution:</strong> As of SDK Tools Revision 17, the virtual machine 327 then you cannot use virtual machine acceleration.</p> 335 machine:</p> 342 virtual machine, such as a VirtualBox or VMWare-hosted virtual machine. You must run the emulator 345 your system such as VirtualBox or VMWare, you may need to unload the driver for that virtual machine 351 <p>To use virtual machine acceleration with the emulator, you need the following version of Android 380 <p>Virtual machine acceleration for Windows requires the installation of the Intel Hardware [all …]
|
/frameworks/base/docs/html/tools/performance/hierarchy-viewer/ |
D | setup.jd | 41 variable on your development machine. For more information,
|
/frameworks/compile/libbcc/ |
D | README.rst | 26 into machine code 142 magic word, version, machine integer type information (the endianness,
|