Initial draft of PNaCl bitcode files.

native_client_sdk/doc_generated/reference/pnacl-c-cpp-language-support.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="pnacl-c-c-language-support">
 <h1 id="pnacl-c-c-language-support">PNaCl C/C++ Language Support</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#source-language-support" id="id3">Source language support</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#versions" id="id4">Versions</a></li>
 <li><a class="reference internal" href="#preprocessor-definitions" id="id5">Preprocessor definitions</a></li>
@@ skipping 350 matching lines @@
   v4s tmp = {shift_amount};
   return shift_me &gt;&gt; __builtin_shuffle_vector(tmp, tmp, 0, 0, 0, 0);
 }
 </pre>
 <h3 id="auto-vectorization">Auto-Vectorization</h3>
 <p>Auto-vectorization is currently not enabled for Portable Native Client,
 but will be in a future release.</p>
 <h2 id="undefined-behavior">Undefined Behavior</h2>
 <p>The C and C++ languages expose some undefined behavior which is
 discussed in <a class="reference internal" href="/native-client/reference/pnacl-undefined-behavior.html#undefined-behavior"><em>PNaCl Undefined Behavior</em></a>.</p>
-<h2 id="floating-point">Floating-Point</h2>
+<h2 id="floating-point"><span id="c-cpp-floating-point"></span>Floating-Point</h2>
 <p>PNaCl exposes 32-bit and 64-bit floating point operations which are
 mostly IEEE-754 compliant. There are a few caveats:</p>
 <ul class="small-gap">
 <li>Some <a class="reference internal" href="/native-client/reference/pnacl-undefined-behavior.html#undefined-behavior-fp"><em>floating-point behavior is currently left as undefined</em></a>.</li>
 <li>The default rounding mode is round-to-nearest and other rounding modes
 are currently not usable, which isn&#8217;t IEEE-754 compliant. PNaCl could
 support switching modes (the 4 modes exposed by C99 <code>FLT_ROUNDS</code>
 macros).</li>
 <li>Signaling <code>NaN</code> never fault.</li>
 <li><p class="first">Fast-math optimizations are currently supported before <em>pexe</em> creation
@@ skipping 50 matching lines @@
 <p>Neither PNaCl nor NaCl currently support asynchronous interruption
 or suspension of threads.</p>
 </li>
 </ul>
 <p>If PNaCl were to support either of these, the interaction of
 <code>volatile</code> and atomics with same-thread signal handling would need
 to be carefully detailed.</p>
 </section>
 
 {{/partials.standard_nacl_article}}