What is Native Client Good For?
Development Environments and Tools
Openness, and Supported Architectures and Languages
.nexes?.nexe to load?.nexes?.nexe to load?For more details, refer to the history behind and comparison of NaCl and PNaCl.
-See NaCl and PNaCl. In short: PNaCl works on the Open +Web platform delivered by Chrome whereas NaCl only works on the Chrome Web +Store.
+The following are some typical use cases. For details, see the Technical Overview.
Using compute-intensive applications, including threads and SIMD, such as:
+Native Client is a versatile technology; we expect that it will also be +
Portable Native Client and Native Client are versatile technologies which are used in many other contexts outside of Chrome.
-See NaCl and PNaCl. In short: PNaCl works on the -open web whereas NaCl only works on the Chrome Web Store.
Fast! The SPEC2k benchmarks (C, C++ and floating-point benchmarks) give @@ -173,6 +178,7 @@
For details, see:
You can develop on Windows, Mac, or Linux, and the resulting Native -Client or Portable Native Client application will run inside the Google -Chrome browser on all those platforms as well as ChromeOS. You can also -develop on ChromeOS with Crouton, and we’re working on -self-hosting a full development environment on Portable Native Client.
+You can develop on Windows, Mac, or Linux, and the resulting Native Client or +Portable Native Client application will run inside the Google Chrome browser on +all those platforms as well as ChromeOS. You can also develop on ChromeOS with +Crouton or our experimental development environment which runs within NaCl, +and we’re working on self-hosting a full development environment on Portable +Native Client.
Any editor+shell combination should work as well as IDEs like Eclipse, Visual Studio with the Native Client Add-In on Windows, or Xcode on Mac OSX.
You’ll need to learn how to use some tools (like GCC, LLVM, make, Eclipse, +Visual Studio, or Xcode) before you can get very far with the SDK. Try seaching +for an introduction to GCC.
Right now only C and C++ are supported directly by the toolchain in the -SDK. C# and other languages in the .NET family are supported via the -Mono port for Native -Client. Moreover, there are several ongoing projects to support -additional language runtimes (e.g. naclports supports Lua, Python and -Ruby) -as well as to compile more languages to LLVM’s intermediate -representation (e.g. support Haskell with GHC -or support Fortran with flang), or +
Right now only C and C++ are supported directly by the toolchain in the SDK. C# +and other languages in the .NET family are supported via the Mono port for +Native Client. Moreover, there are several ongoing projects to support +additional language runtimes (e.g. naclports supports Lua, Python and Ruby) +as well as to compile more languages to LLVM’s intermediate representation +(e.g. support Halide, Haskell with GHC or support Fortran with flang), or transpile languages to C/C++ (source-to-source compilation).
If you’re interested in getting other languages working, please contact the -Native Client team by way of the native-client-discuss mailing list.
-We aim to support multiple browsers. However, a number of features that we consider requirements for a production-quality system that keeps the user safe are difficult to implement without help from the @@ -274,8 +278,7 @@
NPAPI is not supported by the Native Client SDK, and is deprecated in -Chrome.
+NPAPI is not supported by the Native Client SDK, and is deprecated in Chrome.
Native Client currently supports SSE on x86 and NEON on ARM. Support for @@ -288,13 +291,12 @@
To alert the user regarding their hardware platform’s 3D feature set before loading a large NaCl application, see Vetting the driver in Javascript.
-Some GL extensions are exposed to Native Client applications, see the
-GLES2 file.
-This file is part of the GL wrapper supplied by the library
-ppapi_gles2 which you’ll want to include in your project. In most
-cases extensions map to extensions available on other platforms, or
-differ very slightly (if they differ, the extension is usually CHROMIUM
-or ANGLE instead of EXT).
Some GL extensions are exposed to Native Client applications, see the GLES2
+file. This file is part of the GL wrapper supplied by the library
+ppapi_gles2 which you’ll want to include in your project. In most cases
+extensions map to extensions available on other platforms, or differ very
+slightly (if they differ, the extension is usually CHROMIUM or ANGLE instead of
+EXT).
Native Client and Portable Native Client both support pthreads, @@ -329,9 +331,8 @@
For additional information about privacy and Chrome, see the Google -Chrome privacy policy and the Google -Chrome Terms of Service.
+For additional information about privacy and Chrome, see the Google Chrome +privacy policy and the Google Chrome Terms of Service.
Native Client’s sandbox works by validating the untrusted code (the @@ -357,25 +358,23 @@
.pexe to .nexe translator, a simplified compiler
backend, isn’t trusted: it is validated before executing, and so is its
output.
-In addition to static analysis of untrusted code, the Native Client -runtime also includes an outer sandbox that mediates system calls. For -more details about both sandboxes, see Native Client: A Sandbox for -Portable, Untrusted x86 Code +
In addition to static analysis of untrusted code, the Native Client runtime also +includes an outer sandbox that mediates system calls. For more details about +both sandboxes, see Native Client: A Sandbox for Portable, Untrusted x86 Code (PDF).
Google has taken several steps to ensure that Native Client’s security -works, including:
+Google has taken several steps to ensure that Native Client’s security works, +including:
Google is committed to making Native Client safer than JavaScript and -other popular browser technologies. If you have suggestions for security -improvements, let the team know, by way of the native-client-discuss -mailing list.
+Google is committed to making Native Client safer than JavaScript and other +popular browser technologies. If you have suggestions for security improvements, +let the team know, by way of the native-client-discuss mailing list.
mmap() system call.
Google has ported several third-party libraries to Native Client; such -libraries are available in the naclports project. We encourage you to -contribute libraries to naclports, and/or to host your own ported -libraries, and to let the team know about it when you do.
+Google has ported several third-party libraries to Native Client; such libraries +are available in the naclports project. We encourage you to contribute +libraries to naclports, and/or to host your own ported libraries, and to let the +team know about it on native-client-discuss when you do.
The .nmf, and .nexe or .pexe files must either be served from the
diff --git a/native_client_sdk/src/doc/faq.rst b/native_client_sdk/src/doc/faq.rst
index 37b84fe4be294a..640c79485edf50 100644
--- a/native_client_sdk/src/doc/faq.rst
+++ b/native_client_sdk/src/doc/faq.rst
@@ -70,28 +70,32 @@ Portable Native client further enhances the above:
For more details, refer to the :doc:`history behind and comparison of
NaCl and PNaCl