Searched refs:NaCl (Results 1 - 12 of 12) sorted by relevance
/external/chromium_org/native_client_sdk/src/doc/reference/ |
H A D | index.rst | 6 developing with Native Client, such as the NaCl manifest file format. In 8 want to have a better understanding of how NaCl and PNaCl work under the hood;
|
H A D | nacl-manifest-format.rst | 14 NaCl Manifest File (``nmf``). The ``nmf`` tells the browser where to 152 with the NaCl port of glibc, the main program is specified in the 203 helpful tools for determining library dependencies and generating NaCl manifest
|
/external/chromium_org/ppapi/native_client/tests/nacl_browser/fault_injection/ |
H A D | nacl.scons | 38 # simple and in the same repository as the core NaCl where the fault 52 [('expected_error','"NaCl module load failed: Insufficient memory to load file"')], 59 [('expected_error', '"NaCl module load failed: Operating system platform is not supported"')], 66 [('expected_error', '"NaCl module load failed: Data Execution Prevention is required but is not supported"')],
|
/external/llvm/include/llvm/ADT/ |
H A D | Triple.h | 117 NaCl, // Native Client enumerator in enum:llvm::Triple::OSType 385 /// \brief Tests whether the OS is NaCl (Native Client) 387 return getOS() == Triple::NaCl;
|
/external/chromium_org/native_client_sdk/src/doc/ |
H A D | faq.rst | 11 Client (NaCl) and Portable Native Client (PNaCl, pronounced 60 already supports all architectures NaCl does, and as PNaCl evolves it 71 NaCl and PNaCl <nacl-and-pnacl>`. 76 See :doc:`NaCl and PNaCl <nacl-and-pnacl>`. In short: PNaCl works on the Open 77 Web platform delivered by Chrome whereas NaCl only works on the Chrome Web 167 Crouton_ or our `experimental development environment which runs within NaCl`_, 281 before loading a large NaCl application, see :doc:`Vetting the driver in 504 functions (e.g. open/fopen/read/write/...). See :doc:`Using NaCl I/O 564 .. _experimental development environment which runs within NaCl: https://www.youtube.com/watch?v=OzNuzBDEWzk&list=PLOU2XLYxmsIIwGK7v7jg3gQvIAWJzdat_
|
/external/chromium_org/native_client_sdk/src/tools/ |
H A D | common.mk | 142 # Disable DOS PATH warning when using Cygwin based NaCl tools on Windows. 200 # Compute path to requested NaCl Toolchain 232 # By default this is the NaCl SDK 'lib' folder. 405 # If the requested toolchain is a NaCl or PNaCl toolchain, the use the
|
/external/llvm/lib/Target/X86/ |
H A D | X86Subtarget.h | 292 TargetTriple.getOS() == Triple::NaCl);
|
/external/chromium_org/chrome/browser/content_settings/ |
H A D | content_settings_browsertest.cc | 502 // Ensure NaCl can run. 686 NaCl) { 726 NaCl) {
|
/external/chromium_org/components/nacl/browser/ |
H A D | nacl_browser.cc | 35 // Entries may not be claimed for two main reasons. 1) the NaCl process could 36 // be killed while it is loading. 2) the trusted NaCl plugin opens files using 63 #error Add support for your architecture to NaCl IRT file selection 98 UMA_HISTOGRAM_ENUMERATION("NaCl.ValidationCache.Query", status, 104 UMA_HISTOGRAM_ENUMERATION("NaCl.ValidationCache.Set", status, 121 // allow a NaCl inner sandbox escape. 176 // variable. This allows the NaCl/Chromium integration bot to 179 // variable that the standalone NaCl PPAPI plugin accepts. 188 DLOG(ERROR) << "Failed to locate the plugins directory, NaCl disabled."; 200 LOG(ERROR) << "NaCl proces [all...] |
/external/llvm/lib/Support/ |
H A D | Triple.cpp | 150 case NaCl: return "nacl"; 328 .StartsWith("nacl", Triple::NaCl)
|
/external/clang/lib/Basic/ |
H A D | Targets.cpp | 6092 case llvm::Triple::NaCl: 6125 case llvm::Triple::NaCl: 6158 case llvm::Triple::NaCl: 6198 case llvm::Triple::NaCl: 6343 case llvm::Triple::NaCl: 6382 case llvm::Triple::NaCl:
|
/external/clang/lib/CodeGen/ |
H A D | TargetInfo.cpp | 6599 case llvm::Triple::NaCl: 6659 case llvm::Triple::NaCl:
|
Completed in 321 milliseconds