Initial draft of PNaCl bitcode files.

native_client_sdk/doc_generated/overview.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="technical-overview">
 <span id="overview"></span><h1 id="technical-overview"><span id="overview"></span>Technical Overview</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#why-use-native-client" id="id7">Why use Native Client?</a></li>
 <li><a class="reference internal" href="#benefits-of-native-client" id="id8">Benefits of Native Client</a></li>
 <li><a class="reference internal" href="#common-use-cases" id="id9">Common use cases</a></li>
 <li><p class="first"><a class="reference internal" href="#how-native-client-works" id="id10">How Native Client works</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#toolchains" id="id11">Toolchains</a></li>
 <li><a class="reference internal" href="#security" id="id12">Security</a></li>
-<li><a class="reference internal" href="#portability" id="id13">Portability</a></li>
+<li><a class="reference internal" href="#link-for-pnacl-translator" id="id13">Portability</a></li>
 </ul>
 </li>
 <li><p class="first"><a class="reference internal" href="#structure-of-a-web-application" id="id14">Structure of a web application</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#pepper-plug-in-api" id="id15">Pepper plug-in API</a></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#where-to-start" id="id16">Where to start</a></li>
 </ul>
 
@@ skipping 134 matching lines @@
 interfere with other code running either within the browser or outside it.</li>
 <li>The NaCl validator statically analyzes code before running it to make sure it
 only uses code and data patterns that are permitted and safe.</li>
 </ul>
 <p>These security measures are in addition to the existing sandbox in the
 Chrome browser. The Native Client module always executes in a process with
 restricted permissions. The only interaction between this process and the
 outside world is through defined browser interfaces. Because of the
 combination of the NaCl sandbox and the Chrome sandbox, we say that
 Native Client employs a <strong>double sandbox</strong> design.</p>
-<h3 id="portability"><span id="id6"></span>Portability</h3>
+<h3 id="link-for-pnacl-translator"><span id="portability"></span><span id="id6"></span>Portability</h3>
 <p>Portable Native Client (PNaCl, prounounced &#8220;pinnacle&#8221;) employs state-of-the-art
 compiler technology to compile C/C++ source code to a portable bitcode
 executable (<strong>pexe</strong>). PNaCl bitcode is an OS- and architecture-independent
 format that can be freely distributed on the web and <a class="reference internal" href="#link-nacl-in-web-apps"><em>embedded in web
 applications</em></a>.</p>
 <p>The PNaCl translator is a component embedded in the Chrome browser; its task is
 to run pexe modules. Internally, the translator compiles a pexe to a nexe
 (described above), and then executes the nexe within the Native Client sandbox
 as described above. The translator uses intelligent caching to avoid
 re-compiling the pexe if it was previously compiled on the client&#8217;s browser.</p>
@@ skipping 48 matching lines @@
 <p>Pepper includes both a <a class="reference internal" href="/native-client/c-api.html"><em>C API</em></a> and a <a class="reference internal" href="/native-client/cpp-api.html"><em>C++ API</em></a>.
 The C++ API is a set of bindings written on top of the C API. For additional
 information about Pepper, see <a class="reference external" href="http://code.google.com/p/ppapi/wiki/Concepts">Pepper Concepts</a>.</p>
 <h2 id="where-to-start">Where to start</h2>
 <p>The <a class="reference internal" href="/native-client/quick-start.html"><em>Quick Start</em></a> document provides links to downloads and
 documentation to help you get started with developing and distributing Native
 Client applications.</p>
 </section>
 
 {{/partials.standard_nacl_article}}