native_client_sdk/doc_generated/sdk/release-notes.html - Issue 438403003: [NaCl SDK Docs] Only generate one top-level <section> element.

Unified Diff: native_client_sdk/doc_generated/sdk/release-notes.html

Issue 438403003: [NaCl SDK Docs] Only generate one top-level <section> element. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 6 years, 4 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 side-by-side diff with in-line comments

Download patch

« no previous file with comments | « native_client_sdk/doc_generated/sdk/examples.html ('k') | native_client_sdk/src/doc/_sphinxext/chromesite_builder.py » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: native_client_sdk/doc_generated/sdk/release-notes.html

diff --git a/native_client_sdk/doc_generated/sdk/release-notes.html b/native_client_sdk/doc_generated/sdk/release-notes.html

index bf47bc027302e49238d052e9d8f93d1d985b5a10..57b09e9fe25479dc8e939333a630f189ab4eef8b 100644

--- a/native_client_sdk/doc_generated/sdk/release-notes.html

+++ b/native_client_sdk/doc_generated/sdk/release-notes.html

@@ -2,15 +2,12 @@

<span id="sdk-release-notes"></span><h1 id="release-notes"><span id="sdk-release-notes"></span>Release Notes</h1>

-<section id="chrome-pepper-37-20-june-2014">

<h2 id="chrome-pepper-37-20-june-2014">Chrome/Pepper 37 (20 June 2014)</h2>

-<section id="pnacl">

<h3 id="pnacl">PNaCl</h3>

<li>2–10% translation time improvement.</li>

<li>Improved vector load/store and shuffle performance.</li>

</ul>

-</section><section id="pepper">

<h3 id="pepper">Pepper</h3>

<li>Media Streams Input support.</li>

@@ -18,14 +15,11 @@

<li>Hardware Decode API in development preview.</li>

<li>Sync API in development preview.</li>

</ul>

-</section><section id="sdk">

<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>

-</section></section><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="id1">

<h3 id="id1">PNaCl</h3>

<li>Support <a class="reference external" href="http://clang.llvm.org/docs/LanguageExtensions.html#vectors-and-extended-vectors">LLVM vectors</a>

@@ -34,9 +28,7 @@ vectors through <a class="reference internal" href="/native-client/reference/pna

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="id2">

<h3 id="id2">PNaCl</h3>

<li>Upgraded LLVM to version 3.4.</li>

@@ -44,9 +36,7 @@ Chrome. More SIMD instructions will be added in later releases.</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="id3">

<h3 id="id3">Pepper</h3>

<li>Filesystems can now be passed from JavaScript to NaCl. The resulting

@@ -57,16 +47,13 @@ Chrome, simplifying debugging with PNaCl. See <a class="reference internal" href

<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="id4">

<h3 id="id4">PNaCl</h3>

<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>

<li>PNaCl’s default C++ standard library is now LLVM’s own libc++, based on

@@ -74,7 +61,6 @@ LLVM 3.3. This library now supports optional <code>setjmp</code>/<code>longjmp</

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="id5">

<li>The <code>nacl_io</code> library now includes a FUSE mount.</li>

@@ -82,7 +68,6 @@ for details).</li>

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>

<li>Portable Native Client (PNaCl) is enabled by default in Chrome 31. See

@@ -101,7 +86,6 @@ The PNaCl ABI will remain stable starting with the release of Chrome 31.</li>

</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>

<li>Portable Native Client (PNaCl) is currently available for preview in Chrome

@@ -116,7 +100,6 @@ application, be sure to build your code with the latest version of the Native

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>

<li>Portable Native Client (PNaCl) is currently available for developer preview

@@ -139,11 +122,9 @@ are not supported yet).</li>

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>

<li><p class="first">A number of libraries from the naclports project have been incorporated

@@ -168,7 +149,6 @@ object. The <code>dlopen</code> example has been modified to demonstrate this

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>

<li>Each example now has a single <code>index.html</code> file, instead of multiple HTML

@@ -184,7 +164,6 @@ Release configuration by specifying the following URL in Chrome:

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>

<li>Common makefiles, including <code>tools/common.mk</code>, can now handle source files

@@ -192,12 +171,10 @@ located outside of an application’s root directory. For example, a Makefil

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="id6">

<h3 id="id6">Build tools and toolchains</h3>

<li><p class="first">Makefiles have been changed significantly:</p>

@@ -218,7 +195,6 @@ with all toolchains.</li>

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="id7">

<h3 id="id7">Libraries</h3>

<li>The nacl_mounts library has been renamed <strong>nacl_io</strong>, and has been expanded

@@ -226,7 +202,6 @@ 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="id8">

<h3 id="id8">Examples</h3>

<li>A new example, <strong>hello_world_instance3d</strong>, has been added to demonstrate a

@@ -235,14 +210,12 @@ 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>

<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

@@ -251,7 +224,6 @@ which provides a virtual file system that you can use with standard C file

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="id9">

<h3 id="id9">Build tools and toolchains</h3>

<li><p class="first">The SDK includes a new toolchain to build Native Client executables (.nexe

@@ -275,7 +247,6 @@ Native Client manifest (.nmf file) that references those three .nexe files.</li>

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>

@@ -290,7 +261,6 @@ For a C++ example of how to use the MessageLoop API, see

cannot make asynchronous PPAPI calls on a background thread without creating

and using a message loop.</li>

</ul>

-</section><section id="id10">

<h3 id="id10">Libraries</h3>

<p>The SDK includes two new libraries:</p>

@@ -325,7 +295,6 @@ how to use ppapi_main, see examples/hello_world_stdio.</li>

<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="id11">

<h3 id="id11">Examples</h3>

<li><p class="first">The SDK includes two new examples:</p>

@@ -362,13 +331,11 @@ Chrome is closed, the local server is shut down as well.</li>

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="id12">

<h3 id="id12">Build tools and toolchains</h3>

<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

@@ -385,7 +352,6 @@ determine the architecture of .nexe files. That means you can change the

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="id14">

<h3 id="id14">Examples</h3>

<li>The SDK examples now build with four toolchains: the glibc and newlib

@@ -397,7 +363,6 @@ builds both a debug and a release version.</li>

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="id15">

<h3 id="id15">PPAPI</h3>

<li>When creating a 3D rendering context, the <a class="reference external" href="/native-client/pepper_stable/c/group___enums#ga7df48e1c55f6401beea2a1b9c07967e8">attribute list</a>

@@ -405,7 +370,6 @@ 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>

<li>The Windows SDK includes the pthreads-win32 library to assist in porting from

@@ -414,13 +378,11 @@ plug-in (.dll). See pepper_24/include/win/pthread.h and

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>

<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,

@@ -432,7 +394,6 @@ system, and a “<code>*</code>” if the bundle has an update available

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>

<li><p class="first">Developers using the Linux SDK now have resources, including pre-built

@@ -474,7 +435,6 @@ Note that you must set the <code>CHROME_PATH</code> environment variable and sta

</ul>

</li>

</ul>

-</section><section id="id16">

<h3 id="id16">Examples</h3>

<li>On Linux and Windows systems, most of the examples now build with three

@@ -491,7 +451,6 @@ onclick="..."></code>). See <a class="reference external" href="/e

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="id17">

<h3 id="id17">PPAPI</h3>

<li><a class="reference external" href="/native-client/pepper_stable/c/group___enums#ga21b811ac0484a214a8751aa3e1c959d9">PP_InputEvent_Modifier</a>

@@ -499,12 +458,10 @@ 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="id18">

<h3 id="id18">Tools</h3>

<li>The SDK now includes a <strong>command-line debugger</strong> that you can use to debug

@@ -512,7 +469,6 @@ Native Client modules. See <a class="reference internal" href="/native-client/de

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="id19">

<h3 id="id19">Windows SDK</h3>

<li><p class="first">Developers using the Windows SDK can now <strong>build a module as a Pepper

@@ -561,7 +517,6 @@ or <a class="reference external" href="http://www.chromium.org/nativeclient/how-

In the future, the SDK will include resources for hosted development on Mac

and Linux as well as Windows.

</aside>

-</section><section id="id20">

<h3 id="id20">Examples</h3>

<li>Each example in the SDK now builds both a debug and a release version. As

@@ -576,13 +531,12 @@ in each example’s web page, attaches event listeners to monitor the loadin

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="id21">

<h3 id="id21">PPAPI</h3>

<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>

« no previous file with comments | « native_client_sdk/doc_generated/sdk/examples.html ('k') | native_client_sdk/src/doc/_sphinxext/chromesite_builder.py » ('j') | no next file with comments »