NaCl docs: update computed goto support

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="id2">Source language support</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#preprocessor-definitions" id="id3">Preprocessor definitions</a></li>
 </ul>
 </li>
 <li><p class="first"><a class="reference internal" href="#memory-model-and-atomics" id="id4">Memory Model and Atomics</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#memory-model-for-concurrent-operations" id="id5">Memory Model for Concurrent Operations</a></li>
 <li><a class="reference internal" href="#atomic-memory-ordering-constraints" id="id6">Atomic Memory Ordering Constraints</a></li>
 <li><a class="reference internal" href="#volatile-memory-accesses" id="id7">Volatile Memory Accesses</a></li>
 </ul>
 </li>
 <li><a class="reference internal" href="#threading" id="id8">Threading</a></li>
 <li><a class="reference internal" href="#setjmp-and-longjmp" id="id9"><code>setjmp</code> and <code>longjmp</code></a></li>
 <li><a class="reference internal" href="#c-exception-handling" id="id10">C++ Exception Handling</a></li>
 <li><a class="reference internal" href="#inline-assembly" id="id11">Inline Assembly</a></li>
 <li><a class="reference internal" href="#undefined-behavior" id="id12">Undefined Behavior</a></li>
 <li><a class="reference internal" href="#floating-point" id="id13">Floating-Point</a></li>
-<li><p class="first"><a class="reference internal" href="#future-directions" id="id14">Future Directions</a></p>
+<li><a class="reference internal" href="#computed-goto" id="id14">Computed <code>goto</code></a></li>
+<li><p class="first"><a class="reference internal" href="#future-directions" id="id15">Future Directions</a></p>
 <ul class="small-gap">
-<li><a class="reference internal" href="#simd" id="id15">SIMD</a></li>
-<li><a class="reference internal" href="#inter-process-communication" id="id16">Inter-Process Communication</a></li>
-<li><a class="reference internal" href="#posix-style-signal-handling" id="id17">POSIX-style Signal Handling</a></li>
-<li><a class="reference internal" href="#computed-goto" id="id18">Computed <code>goto</code></a></li>
+<li><a class="reference internal" href="#simd" id="id16">SIMD</a></li>
+<li><a class="reference internal" href="#inter-process-communication" id="id17">Inter-Process Communication</a></li>
+<li><a class="reference internal" href="#posix-style-signal-handling" id="id18">POSIX-style Signal Handling</a></li>
 </ul>
 </li>
 </ul>
 
 </div><section id="source-language-support">
 <h2 id="source-language-support">Source language support</h2>
 <p>The currently supported languages are C and C++. The PNaCl toolchain is
 based on Clang 3.3, which fully supports C++11 and most of C11. A
 detailed status of the language support is available <a class="reference external" href="http://clang.llvm.org/cxx_status.html">here</a>.</p>
 <p>For information on using languages other than C/C++, see the <a class="reference internal" href="/native-client/faq.html#other-languages"><em>FAQ
@@ skipping 157 matching lines @@
 emulated. PNaCl could (but currently doesn&#8217;t) only generate them in
 the backend if fast-math were specified and the hardware supports
 the operation.</li>
 <li>Transcendentals aren&#8217;t exposed by PNaCl&#8217;s ABI; they are part of the
 math library that is included in the <em>pexe</em>. PNaCl could, but
 currently doesn&#8217;t, use hardware support if fast-math were provided
 in the <em>pexe</em>.</li>
 </ul>
 </li>
 </ul>
+</section><section id="computed-goto">
+<h2 id="computed-goto">Computed <code>goto</code></h2>
+<p>PNaCl supports computed <code>goto</code>, a non-standard GCC extension to C used
+by some interpreters, by lowering them to <code>switch</code> statements. The
+resulting use of <code>switch</code> might not be as fast as the original
+indirect branches. If you are compiling a program that has a
+compile-time option for using computed <code>goto</code>, it&#8217;s possible that the
+program will run faster with the option turned off (e.g., if the program
+does extra work to take advantage of computed <code>goto</code>).</p>
+<p>NaCl supports computed <code>goto</code> without any transformation.</p>
 </section><section id="future-directions">
 <h2 id="future-directions">Future Directions</h2>
 <section id="simd">
 <h3 id="simd">SIMD</h3>
 <p>PNaCl currently doesn&#8217;t support SIMD. We plan to add SIMD support in the
 very near future.</p>
 <p>NaCl supports SIMD.</p>
 </section><section id="inter-process-communication">
 <h3 id="inter-process-communication">Inter-Process Communication</h3>
 <p>Inter-process communication through shared memory is currently not
@@ skipping 18 matching lines @@
 <p>A similar feature is <strong>thread suspension</strong>: The ability to
 asynchronously suspend and resume a thread and inspect or modify its
 execution state (such as register state).</p>
 <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><section id="computed-goto">
-<h3 id="computed-goto">Computed <code>goto</code></h3>
-<p>PNaCl currently doesn&#8217;t support computed <code>goto</code>, a non-standard
-extension to C used by some interpreters.</p>
-<p>NaCl supports computed <code>goto</code>.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}