Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(733)

Side by Side Diff: native_client_sdk/doc_generated/sdk/release-notes.html

Issue 1059423002: Add PNaCl release note about how to try out Subzero / which flag to set. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: rebase Created 5 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 {{+bindTo:partials.standard_nacl_article}} 1 {{+bindTo:partials.standard_nacl_article}}
2 2
3 <section id="release-notes"> 3 <section id="release-notes">
4 <span id="sdk-release-notes"></span><h1 id="release-notes"><span id="sdk-release -notes"></span>Release Notes</h1> 4 <span id="sdk-release-notes"></span><h1 id="release-notes"><span id="sdk-release -notes"></span>Release Notes</h1>
5 <p>The dates in the following release notes denote when Chrome and the NaCl SDK 5 <p>The dates in the following release notes denote when Chrome and the NaCl SDK
6 reached canary status. The stable release is typically 6 weeks later.</p> 6 reached canary status. The stable release is typically 6 weeks later.</p>
7 <h2 id="chrome-pepper-43-03-april-2015">Chrome/Pepper 43 (03 April 2015)</h2> 7 <h2 id="chrome-pepper-43-03-april-2015">Chrome/Pepper 43 (03 April 2015)</h2>
8 <h3 id="pnacl">PNaCl</h3> 8 <h3 id="pnacl">PNaCl</h3>
9 <ul class="small-gap"> 9 <ul class="small-gap">
10 <li>The C11/C++11 <code>acquire</code>, <code>release</code>, and <code>acq_rel< /code> memory orders are now 10 <li>The C11/C++11 <code>acquire</code>, <code>release</code>, and <code>acq_rel< /code> memory orders are now
11 generated by default. The in-browser Chrome 42 translator supports them, the 11 generated by default. The in-browser Chrome 42 translator supports them, the
12 SDK can therefore generate them.</li> 12 SDK can therefore generate them.</li>
13 <li>Fix a <a class="reference external" href="https://code.google.com/p/chromium /issues/detail?id=460432">code generation bug on ARM</a> when dealing with 16-bi t load/store and 13 <li>Fix a <a class="reference external" href="https://code.google.com/p/chromium /issues/detail?id=460432">code generation bug on ARM</a> when dealing with 16-bi t load/store and
14 <code>bswap</code> which led to a NaCl validation failure.</li> 14 <code>bswap</code> which led to a NaCl validation failure.</li>
15 <li>PNaCl is now based on LLVM 3.6. If you are using GDB to debug PNaCl 15 <li>PNaCl is now based on LLVM 3.6. If you are using GDB to debug PNaCl
16 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.h tml#debugging-pnacl-pexes"><em>BC files with debug metadata in the browser</em>< /a>, 16 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.h tml#debugging-pnacl-pexes"><em>BC files with debug metadata in the browser</em>< /a>,
17 remember that debug info from SDK version <code>X</code> is only compatible with the 17 remember that debug info from SDK version <code>X</code> is only compatible with the
18 PNaCl translator in chrome version <code>X</code>. The bitcode debug metadata fo rmat 18 PNaCl translator in chrome version <code>X</code>. The bitcode debug metadata fo rmat
19 changed from LLVM 3.5 to 3.6. If you need to debug an app built with SDK 19 changed from LLVM 3.5 to 3.6. If you need to debug an app built with SDK
20 version <code>X</code> running in Chrome version <code>Y</code> (with <code>X != Y</code>), it is still 20 version <code>X</code> running in Chrome version <code>Y</code> (with <code>X != Y</code>), it is still
21 possible to do so. Simply translate the pexe to a nexe using the 21 possible to do so. Simply translate the pexe to a nexe using the
22 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.h tml#debugging-pexes-via-nexes"><em>offline pnacl-translate tool from SDK version X</em></a> instead of using the translator in the 22 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.h tml#debugging-pexes-via-nexes"><em>offline pnacl-translate tool from SDK version X</em></a> instead of using the translator in the
23 browser (version <code>Y</code>).</li> 23 browser (version <code>Y</code>).</li>
24 <li>PNaCl&#8217;s support for use of libstdc++ 4.6 as the C++ standard library i s 24 <li>PNaCl&#8217;s support for use of libstdc++ 4.6 as the C++ standard library i s
25 deprecated and will be removed in the next release. PNaCl has used libc++ 25 deprecated and will be removed in the next release. PNaCl has used libc++
26 (which is much more up-to-date, currently based on LLVM 3.6) as the default 26 (which is much more up-to-date, currently based on LLVM 3.6) as the default
27 since Pepper 33.</li> 27 since Pepper 33.</li>
28 <li>PNaCl&#8217;s experimental <a class="reference external" href="https://chrom ium.googlesource.com/native_client/pnacl-subzero/+/master/README.rst">Subzero tr anslator</a> is available for x86-32 NaCl in
29 Chrome version 43, behind a flag. To give it a try, run Chrome with the
30 <code>--enable-pnacl-subzero</code> commandline flag, and use the <code>optlevel 0</code>
31 <a class="reference internal" href="/native-client/reference/nacl-manifest-forma t.html#pnacl-nmf-optlevels"><em>NaCl manifest option</em></a>. Application start up time
32 should be several times faster than the previous LLVM-based <code>optlevel 0</co de>
33 mode, with similar code quality. Note that x86-32 NaCl requires a 32-bit
34 Chrome. On Windows, it also requires a 32-bit Windows OS, but 64-bit Linux
35 OSes can run x86-32 NaCl. If you try it out, please send us feedback
36 on <a class="reference external" href="https://groups.google.com/forum/#!forum/n ative-client-dev">native-client-dev</a>. We are working on improvements and addi ng
37 new targets.</li>
28 </ul> 38 </ul>
29 <h3 id="pepper">Pepper</h3> 39 <h3 id="pepper">Pepper</h3>
30 <ul class="small-gap"> 40 <ul class="small-gap">
31 <li>UDP Socket Multicast API in development preview (PPB_UDP_SOCKET 1.2).</li> 41 <li>UDP Socket Multicast API in development preview (PPB_UDP_SOCKET 1.2).</li>
32 <li>Hardware Video Encoder API in development preview (PPB_VIDEO_ENCODER 0.1).</ li> 42 <li>Hardware Video Encoder API in development preview (PPB_VIDEO_ENCODER 0.1).</ li>
33 </ul> 43 </ul>
34 <h2 id="chrome-pepper-42-20-february-2015">Chrome/Pepper 42 (20 February 2015)</ h2> 44 <h2 id="chrome-pepper-42-20-february-2015">Chrome/Pepper 42 (20 February 2015)</ h2>
35 <h3 id="sdk">SDK</h3> 45 <h3 id="sdk">SDK</h3>
36 <ul class="small-gap"> 46 <ul class="small-gap">
37 <li>The SDK now contains experimental versions of <code>i686-nacl-clang</code>, 47 <li>The SDK now contains experimental versions of <code>i686-nacl-clang</code>,
(...skipping 588 matching lines...) Expand 10 before | Expand all | Expand 10 after
626 </ul> 636 </ul>
627 <h3 id="id30">PPAPI</h3> 637 <h3 id="id30">PPAPI</h3>
628 <ul class="small-gap"> 638 <ul class="small-gap">
629 <li>The <code>CompletionCallbackFactory</code> class template now takes a thread traits 639 <li>The <code>CompletionCallbackFactory</code> class template now takes a thread traits
630 class as its second parameter. For details see the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_completion_callback_factory# details">CompletionCallbackFactory 640 class as its second parameter. For details see the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_completion_callback_factory# details">CompletionCallbackFactory
631 class template reference</a>.</li> 641 class template reference</a>.</li>
632 </ul> 642 </ul>
633 </section> 643 </section>
634 644
635 {{/partials.standard_nacl_article}} 645 {{/partials.standard_nacl_article}}
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698