PNaCl documentation: add SIMD vectors.

native_client_sdk/doc_generated/faq.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="frequently-asked-questions">
 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#what-is-native-client-good-for" id="id3">What is Native Client Good For?</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#why-did-google-build-native-client" id="id4">Why did Google build Native Client?</a></li>
 <li><a class="reference internal" href="#when-should-i-use-native-client" id="id5">When should I use Native Client?</a></li>
@@ skipping 150 matching lines @@
 </tr>
 <tr class="row-odd"><td>ARM</td>
 <td>10%</td>
 </tr>
 </tbody>
 </table>
 <p>Note that benchmark performance is sometimes bimodal, so different use
 cases are likely to achieve better or worse performance than the above
 averages. For example floating-point heavy code usually exhibits much
 lower overheads whereas very branch-heavy code often performs worse.</p>
+<p>Note that PNaCl supports performance features that are often used in
+native code such as <a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html#language-support-threading"><em>threading</em></a> and
+<a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html#portable-simd-vectors"><em>Portable SIMD Vectors</em></a>.</p>
 <p>For details, see:</p>
 <ul class="small-gap">
 <li><a class="reference external" href="https://nativeclient.googlecode.com/svn/data/site/NaCl_SFI.pdf">Adapting Software Fault Isolation to Contemporary CPU Architectures</a> (PDF).</li>
 <li><a class="reference external" href="http://research.google.com/pubs/pub34913.html">Native Client: A Sandbox for Portable, Untrusted x86 Code</a> (PDF).</li>
 </ul>
 <p>If your code isn&#8217;t performing as close to native speed as you&#8217;d expect,
 <a class="reference internal" href="/native-client/help.html"><em>let us know</em></a>!</p>
 </section><section id="why-use-portable-native-client-instead-of-technology-x">
 <h3 id="why-use-portable-native-client-instead-of-technology-x">Why use Portable Native Client instead of <em>&lt;technology X&gt;</em>?</h3>
 <p>Many other technologies can be compared to Portable Native Client:
@@ skipping 89 matching lines @@
 handling, out-of-process plugins, and asynchronous interfaces. Native
 Client has transitioned from using NPAPI to using Pepper.</p>
 </section><section id="is-npapi-part-of-the-native-client-sdk">
 <h3 id="is-npapi-part-of-the-native-client-sdk">Is NPAPI part of the Native Client SDK?</h3>
 <p>NPAPI is not supported by the Native Client SDK, and is <a class="reference external" href="http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html">deprecated in
 Chrome</a>.</p>
 </section><section id="does-native-client-support-simd-vector-instructions">
 <h3 id="does-native-client-support-simd-vector-instructions">Does Native Client support SIMD vector instructions?</h3>
 <p>Native Client currently supports SSE on x86 and NEON on ARM. Support for
 AVX on x86 is under way.</p>
-<p>Portable Native Client should support SIMD vectors in the near future.</p>
+<p>Portable Native Client supports portable SIMD vectors, as detailed in
+<a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html#portable-simd-vectors"><em>Portable SIMD Vectors</em></a>.</p>
 </section><section id="can-i-use-native-client-for-3d-graphics">
 <h3 id="can-i-use-native-client-for-3d-graphics">Can I use Native Client for 3D graphics?</h3>
 <p>Yes. Native Client supports <a class="reference external" href="https://www.khronos.org/opengles/">OpenGL ES 2.0</a>.</p>
 <p>To alert the user regarding their hardware platform&#8217;s 3D feature set
 before loading a large NaCl application, see <a class="reference internal" href="/native-client/devguide/coding/3D-graphics.html"><em>Vetting the driver in
 Javascript</em></a>.</p>
 <p>Some GL extensions are exposed to Native Client applications, see the
 <a class="reference external" href="https://src.chromium.org/viewvc/chrome/trunk/src/ppapi/lib/gl/gles2/gles2.c">GLES2 file</a>.
 This file is part of the GL wrapper supplied by the library
 <code>ppapi_gles2</code> which you&#8217;ll want to include in your project.  In most
@@ skipping 217 matching lines @@
 you&#8217;re loading the correct <code>.nexe</code> file by building a separate
 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest file to
 let the browser select the correct <code>.nexe</code> file. Note: the need to
 select a processor-specific <code>.nexe</code> goes away with Portable Native
 Client.</li>
 <li>If things still aren&#8217;t working, <a class="reference internal" href="/native-client/help.html"><em>ask for help</em></a>!</li>
 </ul>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}