<section id="release-notes">
<span id="sdk-release-notes"></span><h1 id="release-notes"><span id="sdk-release-notes"></span>Release Notes</h1>
-<section id="chrome-pepper-36-09-may-2014">
-<h2 id="chrome-pepper-36-09-may-2014">Chrome/Pepper 36 (09 May 2014)</h2>
-<section id="pnacl">
+<h2 id="chrome-pepper-37-20-june-2014">Chrome/Pepper 37 (20 June 2014)</h2>
<h3 id="pnacl">PNaCl</h3>
<ul class="small-gap">
+<li>2–10% translation time improvement.</li>
+<li>Improved vector load/store and shuffle performance.</li>
+</ul>
+<h3 id="pepper">Pepper</h3>
+<ul class="small-gap">
+<li>Media Streams Input support.</li>
+<li>Compositor API.</li>
+<li>Hardware Decode API in development preview.</li>
+<li>Sync API in development preview.</li>
+</ul>
+<h3 id="sdk">SDK</h3>
+<ul class="small-gap">
+<li>Demo of a <a class="reference internal" href="/native-client/io2014.html#io2014"><em>full development environment in the browser</em></a>.</li>
+</ul>
+<h2 id="chrome-pepper-36-09-may-2014">Chrome/Pepper 36 (09 May 2014)</h2>
+<h3 id="id1">PNaCl</h3>
+<ul class="small-gap">
<li>Support <a class="reference external" href="http://clang.llvm.org/docs/LanguageExtensions.html#vectors-and-extended-vectors">LLVM vectors</a>
and <a class="reference external" href="http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html">GCC vectors</a> for SIMD
vectors through <a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html#portable-simd-vectors"><em>Portable SIMD Vectors</em></a>. Note that this is still an early release,
and performance is expected to become acceptable for version 37 of
Chrome. More SIMD instructions will be added in later releases.</li>
</ul>
-</section></section><section id="chrome-pepper-35-31-mar-2014">
<h2 id="chrome-pepper-35-31-mar-2014">Chrome/Pepper 35 (31 Mar 2014)</h2>
-<section id="id1">
-<h3 id="id1">PNaCl</h3>
+<h3 id="id2">PNaCl</h3>
<ul class="small-gap">
<li>Upgraded LLVM to version 3.4.</li>
<li>Translation now uses dynamic load balancing, making translation time faster.</li>
<li>Unstable pexes (i.e. non-finalized) with debug information can be loaded by
Chrome, simplifying debugging with PNaCl. See <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#debugging-pnacl-pexes"><em>Debugging PNaCl pexes</em></a></li>
</ul>
-</section></section><section id="chrome-pepper-34-20-feb-2014">
<h2 id="chrome-pepper-34-20-feb-2014">Chrome/Pepper 34 (20 Feb 2014)</h2>
-<section id="pepper">
-<h3 id="pepper">Pepper</h3>
+<h3 id="id3">Pepper</h3>
<ul class="small-gap">
<li>Filesystems can now be passed from JavaScript to NaCl. The resulting
<code>pp::Var</code> will contain a <code>pp::Resource</code> that can be given to the
<a class="reference external" href="/native-client/pepper_dev/cpp/classpp_1_1_media_stream_video_track">pp::MediaStreamVideoTrack</a> for
more details.</li>
</ul>
-</section><section id="id2">
-<h3 id="id2">PNaCl</h3>
+<h3 id="id4">PNaCl</h3>
<ul class="small-gap">
<li>Parallel translation: at least 1.7x faster, even with older pexes.</li>
<li>Intelligent abbreviations in the bitcode: 20% reduction in binary size using
the <a class="reference internal" href="/native-client/devguide/devcycle/building.html#pnacl-compress"><em>pnacl-compress</em></a> tool.</li>
</ul>
-</section></section><section id="chrome-pepper-33-16-dec-2013">
<h2 id="chrome-pepper-33-16-dec-2013">Chrome/Pepper 33 (16 Dec 2013)</h2>
-<section id="portable-native-client">
<h3 id="portable-native-client">Portable Native Client</h3>
<ul class="small-gap">
<li>PNaCl’s default C++ standard library is now LLVM’s own libc++, based on
handling (see <a class="reference external" href="https://groups.google.com/forum/#!topic/native-client-discuss/0spfg6O04FM">announcement</a>
for details).</li>
</ul>
-</section><section id="sdk">
-<h3 id="sdk">SDK</h3>
+<h3 id="id5">SDK</h3>
<ul class="small-gap">
<li>The <code>nacl_io</code> library now includes a FUSE mount.</li>
<li>In the SDK examples, <code>common.js</code> now loads the Release version of the
nexes/pexes that are built (by default).</li>
<li>“<code>make debug</code>” and “<code>make run</code>” have been fixed on Mac.</li>
</ul>
-</section></section><section id="pnacl-enabled-by-default-in-chrome-31-12-nov-2013">
<h2 id="pnacl-enabled-by-default-in-chrome-31-12-nov-2013">PNaCl enabled by default in Chrome 31 (12 Nov 2013)</h2>
<ul class="small-gap">
<li>Portable Native Client (PNaCl) is enabled by default in Chrome 31. See
</ul>
</li>
</ul>
-</section><section id="pnacl-in-chrome-30-dev-channel-01-aug-2013">
<h2 id="pnacl-in-chrome-30-dev-channel-01-aug-2013">PNaCl in Chrome 30 Dev channel (01 Aug 2013)</h2>
<ul class="small-gap">
<li>Portable Native Client (PNaCl) is currently available for preview in Chrome
Client SDK.</li>
<li>Update: PNaCl is not enabled by default in beta or stable versions of M30.</li>
</ul>
-</section><section id="pnacl-15-may-2013">
<h2 id="pnacl-15-may-2013">PNaCl (15 May 2013)</h2>
<ul class="small-gap">
<li>Portable Native Client (PNaCl) is currently available for developer preview
of PNaCl. If so, you will need to recompile your application with the pnacl
toolchain in a new SDK bundle.</li>
</ul>
-</section><section id="pepper-27-12-april-2013">
<h2 id="pepper-27-12-april-2013">Pepper 27 (12 April 2013)</h2>
<p>The Pepper 27 bundle features a significant number of new libraries that have
been incorporated directly into the SDK.</p>
-<section id="libraries">
<h3 id="libraries">Libraries</h3>
<ul class="small-gap">
<li><p class="first">A number of libraries from the naclports project have been incorporated
functionality: reverse.cc is built into a shared object (.so) file, which is
downloaded and opened using an <code>httpfs</code> mount.</li>
</ul>
-</section><section id="examples">
<h3 id="examples">Examples</h3>
<ul class="small-gap">
<li>Each example now has a single <code>index.html</code> file, instead of multiple HTML
information about how different NaCl modules are loaded into <code>index.html</code>,
see the <code>common.js</code> file in each example.</li>
</ul>
-</section><section id="build-tools-and-toolchains">
<h3 id="build-tools-and-toolchains">Build tools and toolchains</h3>
<ul class="small-gap">
<li>Common makefiles, including <code>tools/common.mk</code>, can now handle source files
for an application can specify a source file to compile such as
<code>../../some/other/place.cpp</code>.</li>
</ul>
-</section></section><section id="pepper-26-29-march-2013">
<h2 id="pepper-26-29-march-2013">Pepper 26 (29 March 2013)</h2>
<p>The Pepper 26 bundle includes a new HTTP filesystem type in the nacl_mounts
library (which has been renamed nacl_io), changes to the example Makefiles, a
simple new 3D example, and a threaded file IO example.</p>
-<section id="id3">
-<h3 id="id3">Build tools and toolchains</h3>
+<h3 id="id6">Build tools and toolchains</h3>
<ul class="small-gap">
<li><p class="first">Makefiles have been changed significantly:</p>
<ul class="small-gap">
the same set of header files as host builds. Previously host and NaCl builds
used different headers, which could cause build problems.</li>
</ul>
-</section><section id="id4">
-<h3 id="id4">Libraries</h3>
+<h3 id="id7">Libraries</h3>
<ul class="small-gap">
<li>The nacl_mounts library has been renamed <strong>nacl_io</strong>, and has been expanded
with a new type of mount, httpfs, which can be used to read URLs via HTTP.
For details see <code>include/nacl_io/nacl_io.h</code>, as well as the
<code>hello_nacl_io</code> example.</li>
</ul>
-</section><section id="id5">
-<h3 id="id5">Examples</h3>
+<h3 id="id8">Examples</h3>
<ul class="small-gap">
<li>A new example, <strong>hello_world_instance3d</strong>, has been added to demonstrate a
simplified 3D app.</li>
thread. The example demonstrates how to use the MessageLoop API and blocking
callbacks on a thread.</li>
</ul>
-</section><section id="general">
<h3 id="general">General</h3>
<ul class="small-gap">
<li>Old bundles (<code>pepper_20</code> and earlier) have been removed from the Native
Client SDK Manifest, and will no longer be updated by the <code>naclsdk</code>
command.</li>
</ul>
-</section></section><section id="pepper-25-21-december-2012">
<h2 id="pepper-25-21-december-2012">Pepper 25 (21 December 2012)</h2>
<p>The Pepper 25 bundle features an ARM toolchain to build Native Client modules
for ARM devices, two new Pepper APIs (including the MessageLoop API, which lets
operations, and ppapi_main, which lets you implement a Native Client module
using a simple ppapi_main function), and two new examples that demonstrate how
to use the nacl_mounts and ppapi_main libraries.</p>
-<section id="id6">
-<h3 id="id6">Build tools and toolchains</h3>
+<h3 id="id9">Build tools and toolchains</h3>
<ul class="small-gap">
<li><p class="first">The SDK includes a new toolchain to build Native Client executables (.nexe
files) for <strong>ARM devices</strong>.</p>
the <code>examples/</code> directory to the <code>tools/</code> directory. On Windows, you can
run <code>httpd.cmd</code> (in the <code>examples/</code> directory) to start the server.</li>
</ul>
-</section><section id="ppapi">
<h3 id="ppapi">PPAPI</h3>
<p>Pepper 25 includes two new APIs:</p>
<ul class="small-gap">
cannot make asynchronous PPAPI calls on a background thread without creating
and using a message loop.</li>
</ul>
-</section><section id="id7">
-<h3 id="id7">Libraries</h3>
+<h3 id="id10">Libraries</h3>
<p>The SDK includes two new libraries:</p>
<ul class="small-gap">
<li><p class="first">The <strong>nacl_mounts</strong> library provides a virtual file system that your module
<p>Header files for the new libraries are in the <code>include/</code> directory, source
files are in the <code>src/</code> directory, and compiled libraries are in the <code>lib/</code>
directory.</p>
-</section><section id="id8">
-<h3 id="id8">Examples</h3>
+<h3 id="id11">Examples</h3>
<ul class="small-gap">
<li><p class="first">The SDK includes two new examples:</p>
<ul class="small-gap">
source dependencies, and invokes the build rules in a separate file
(common.mk).</li>
</ul>
-</section></section><section id="pepper-24-5-december-2012">
<h2 id="pepper-24-5-december-2012">Pepper 24 (5 December 2012)</h2>
<p>The Pepper 24 bundle features a new, experimental toolchain called PNaCl (short
for “Portable Native Client”), a new library (pthreads-win32) for the Windows
SDK, and an expanded list of attributes for Pepper 3D contexts that lets
applications specify a GPU preference for low power or performance.</p>
-<section id="id9">
-<h3 id="id9">Build tools and toolchains</h3>
+<h3 id="id12">Build tools and toolchains</h3>
<ul class="small-gap">
<li>The SDK includes a new, experimental toolchain called <a class="reference external" href="http://nativeclient.googlecode.com/svn/data/site/pnacl.pdf">PNaCl</a> (pronounced
“pinnacle”). The PNaCl toolchain produces architecture-independent executable
names of your .nexe files and <code>create_nmf.py</code> will still be able to
generate the appropriate Native Client manifest file for your application.</li>
</ul>
-</section><section id="id11">
-<h3 id="id11">Examples</h3>
+<h3 id="id14">Examples</h3>
<ul class="small-gap">
<li>The SDK examples now build with four toolchains: the glibc and newlib
toolchains, the experimental PNaCl toolchain, and the hosted toolchain on
drawing function is now set up as the Flush() callback, which allows 2D
drawing to occur as quickly as possible.</li>
</ul>
-</section><section id="id12">
-<h3 id="id12">PPAPI</h3>
+<h3 id="id15">PPAPI</h3>
<ul class="small-gap">
<li>When creating a 3D rendering context, the <a class="reference external" href="/native-client/pepper_stable/c/group___enums#ga7df48e1c55f6401beea2a1b9c07967e8">attribute list</a>
for the context can specify whether to prefer low power or performance for
the GPU. Contexts with a low power preference may be created on an integrated
GPU; contexts with a performance preference may be created on a discrete GPU.</li>
</ul>
-</section><section id="windows-sdk">
<h3 id="windows-sdk">Windows SDK</h3>
<ul class="small-gap">
<li>The Windows SDK includes the pthreads-win32 library to assist in porting from
pepper_24/src/pthread/README for additional information.</li>
<li>The update utility naclsdk.bat works when it is run from a path with spaces.</li>
</ul>
-</section></section><section id="pepper-23-15-october-2012">
<h2 id="pepper-23-15-october-2012">Pepper 23 (15 October 2012)</h2>
<p>The Pepper 23 bundle includes support for the nacl-gdb debugger on Mac and
32-bit Windows, resources to enable hosted development on Linux, and changes to
make the SDK examples compliant with version 2 of the Chrome Web Store manifest
file format.</p>
-<section id="tools">
<h3 id="tools">Tools</h3>
<ul class="small-gap">
<li>The <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#using-gdb"><em>nacl-gdb debugger</em></a> now works on all systems (Mac,
information about a bundle, use the command <code>naclsdk info <bundle></code> (for
example, <code>naclsdk info pepper_28</code>).</li>
</ul>
-</section><section id="linux-sdk">
<h3 id="linux-sdk">Linux SDK</h3>
<ul class="small-gap">
<li><p class="first">Developers using the Linux SDK now have resources, including pre-built
</ul>
</li>
</ul>
-</section><section id="id13">
-<h3 id="id13">Examples</h3>
+<h3 id="id16">Examples</h3>
<ul class="small-gap">
<li>On Linux and Windows systems, most of the examples now build with three
toolchains: the Native Client glibc and newlib toolchains, and the native
a list of changes between version 1 and version 2 of the manifest file
format, and a support schedule for applications that use version 1.</li>
</ul>
-</section><section id="id14">
-<h3 id="id14">PPAPI</h3>
+<h3 id="id17">PPAPI</h3>
<ul class="small-gap">
<li><a class="reference external" href="/native-client/pepper_stable/c/group___enums#ga21b811ac0484a214a8751aa3e1c959d9">PP_InputEvent_Modifier</a>
has two new enum values (_ISLEFT and _ISRIGHT).</li>
<li>The memory leak in the <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___web_socket__1__0">WebSocket</a> API has
been fixed.</li>
</ul>
-</section></section><section id="pepper-22-22-august-2012">
<h2 id="pepper-22-22-august-2012">Pepper 22 (22 August 2012)</h2>
<p>The Pepper 22 bundle includes a <strong>command-line debugger</strong>, resources to enable
<strong>hosted development on Windows</strong>, and changes to the example Makefiles (each
example now builds both a debug and a release version).</p>
-<section id="id15">
-<h3 id="id15">Tools</h3>
+<h3 id="id18">Tools</h3>
<ul class="small-gap">
<li>The SDK now includes a <strong>command-line debugger</strong> that you can use to debug
Native Client modules. See <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#devcycle-debugging"><em>Debugging with nacl-gdb</em></a> for instructions on how to use this debugger. For now,
nacl-gdb only works on 64-bit Windows, 64-bit Linux, and 32-bit Linux
systems. Support for Mac and 32-bit Windows systems will be added soon.</li>
</ul>
-</section><section id="id16">
-<h3 id="id16">Windows SDK</h3>
+<h3 id="id19">Windows SDK</h3>
<ul class="small-gap">
<li><p class="first">Developers using the Windows SDK can now <strong>build a module as a Pepper
plugin</strong> (sometimes called a “trusted” or “in-process” plugin) using the
In the future, the SDK will include resources for hosted development on Mac
and Linux as well as Windows.
</aside>
-</section><section id="id17">
-<h3 id="id17">Examples</h3>
+<h3 id="id20">Examples</h3>
<ul class="small-gap">
<li>Each example in the SDK now builds both a debug and a release version. As
before, most examples also build newlib and glibc versions, which means that
of the module, and implements handleMessage() to respond to messages sent
from the NaCl module to the JavaScript side of the application</li>
</ul>
-</section><section id="id18">
-<h3 id="id18">PPAPI</h3>
+<h3 id="id21">PPAPI</h3>
<ul class="small-gap">
<li>The <code>CompletionCallbackFactory</code> class template now takes a thread traits
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
class template reference</a>.</li>
</ul>
-</section></section></section>
+</section>
{{/partials.standard_nacl_article}}
projects / platform / framework / web / crosswalk.git / blobdiff