[NaCl SDK] Remove references to naclports bundle

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 145 matching lines @@
 restrictions beyond C&#8217;s.</p>
 <h2 id="c-exception-handling"><span id="exception-handling"></span>C++ Exception Handling</h2>
 <p>PNaCl currently supports C++ exception handling through <code>setjmp()</code> and
 <code>longjmp()</code>, which can be enabled with the <code>--pnacl-exceptions=sjlj</code> linker
 flag (set with <code>LDFLAGS</code> when using Make). Exceptions are disabled by default
 so that faster and smaller code is generated, and <code>throw</code> statements are
 replaced with calls to <code>abort()</code>. The usual <code>-fno-exceptions</code> flag is also
 supported, though the default is <code>-fexceptions</code>. PNaCl will support full
 zero-cost exception handling in the future.</p>
 <aside>
-When using <a class="reference external" href="https://code.google.com/p/naclports">naclports</a> or other prebuilt static libraries, you don&#8217;t
+When using <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a> or other prebuilt static libraries, you don&#8217;t
 need to recompile because the exception handling support is
 implemented at link time (when all the static libraries are put
 together with your application).
 </aside>
 <p>NaCl supports full zero-cost C++ exception handling.</p>
 <h2 id="inline-assembly">Inline Assembly</h2>
 <p>Inline assembly isn&#8217;t supported by PNaCl because it isn&#8217;t portable. The
 one current exception is the common compiler barrier idiom
 <code>asm(&quot;&quot;:::&quot;memory&quot;)</code>, which gets transformed to a sequentially
 consistent memory barrier (equivalent to <code>__sync_synchronize()</code>). In
@@ skipping 261 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}}