Update NaCl SDK release notes for M45

Review URL: https://codereview.chromium.org/1230793006

Cr-Commit-Position: refs/heads/master@{#338144}

3 files changed, 42 insertions, 36 deletions

diff --git a/native_client_sdk/doc_generated/community/security-contest/contest-faq.html b/native_client_sdk/doc_generated/community/security-contest/contest-faq.html
index e1aed53..2c78240 100644
--- a/native_client_sdk/doc_generated/community/security-contest/contest-faq.html
+++ b/native_client_sdk/doc_generated/community/security-contest/contest-faq.html
@@ -199,12 +199,12 @@ member of a different team, then you can remove yourself from the list
 of team members of that particular team.</p>
 <h2 id="i-tried-to-sign-up-and-it-seems-someone-who-wants-to-be-a-member-of-my-team-has-already-registered-with-another-team-what-can-we-do">I tried to sign up and it seems someone who wants to be a member of my team has already registered with another team. What can we do?</h2>
 <p>If everyone in your potential teammate&#8217;s original team (including
-himself/herself) has accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> of the contest, then unfortunately you will have to
+themselves) has accepted the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and Conditions</em></a> of the contest, then unfortunately you will have to
 look for other potential partners. Otherwise, your potential teammate
-can remove himself from the other team. All he/she will need to do is
-to reply to one of the registration emails he/she received (it should
+can remove themselves from the other team. All they will need to do is
+to reply to one of the registration emails they received (it should
 be sent to <a class="reference external" href="mailto:nacl-security-contest&#37;&#52;&#48;google&#46;com">nacl-security-contest<span>&#64;</span>google<span>&#46;</span>com</a>) and indicate the changes
-to be made. Please note that this will mean that his/her team members
+to be made. Please note that this will mean that their team members
 will receive an email notifying them of the changes in the team&#8217;s
 composition and asking them to re-accept the <a class="reference internal" href="/native-client/community/security-contest/contest-terms.html"><em>Terms and
 Conditions</em></a>. All team members of that team will need
@@ -245,7 +245,7 @@ taken into account by our judges.</p>
 <p>We want to make sure that we use our judges&#8217; time wisely. Rather than
 having them review hundreds of similar or small scale bugs, sometimes
 identified with the same automatic process, we are limiting the number
-of issues that each participant can submit in his/her/their summary.</p>
+of issues that each participant can submit in their summary.</p>
 <h2 id="my-english-is-not-great-will-this-count-against-me-in-the-judging-process">My English is not great&#8212;will this count against me in the judging process?</h2>
 <p>Entries in languages other than in English or entries that are deemed
 incomprehensible by the judges will not be reviewed. We do not plan to
@@ -272,7 +272,7 @@ interesting by continuously raising the bar of bug finding.</p>
 <p>If the contest has not ended, you may submit an updated summary. You
 may not submit an updated summary once the contest has ended.</p>
 <h2 id="someone-from-our-team-submitted-a-summary-on-behalf-of-our-team-without-consulting-with-everyone-else-how-can-we-ensure-that-the-judges-will-use-the-previous-summary-and-not-the-last-one">Someone from our team submitted a summary on behalf of our team without consulting with everyone else. How can we ensure that the judges will use the previous summary and not the last one?</h2>
-<p>If your team member submitted his / her version of the team&#8217;s summary
+<p>If your team member submitted their version of the team&#8217;s summary
 before the end date of the contest, and if this is the last summary
 that was submitted from your team, then the Judges will disregard all
 previous versions of your summary and will only review this last
diff --git a/native_client_sdk/doc_generated/sdk/release-notes.html b/native_client_sdk/doc_generated/sdk/release-notes.html
index a96ec9f..5a8dc1b 100644
--- a/native_client_sdk/doc_generated/sdk/release-notes.html
+++ b/native_client_sdk/doc_generated/sdk/release-notes.html
@@ -4,6 +4,11 @@
 <span id="sdk-release-notes"></span><h1 id="release-notes"><span id="sdk-release-notes"></span>Release Notes</h1>
 <p>The dates in the following release notes denote when Chrome and the NaCl SDK
 reached canary status. The stable release is typically 6 weeks later.</p>
+<h2 id="chrome-pepper-45-10-july-2015">Chrome/Pepper 45 (10 July 2015)</h2>
+<h3 id="pepper">Pepper</h3>
+<ul class="small-gap">
+<li>UDP Socket Multicast API in stable (PPB_UDP_SOCKET 1.2).</li>
+</ul>
 <h2 id="chrome-pepper-43-03-april-2015">Chrome/Pepper 43 (03 April 2015)</h2>
 <h3 id="pnacl">PNaCl</h3>
 <ul class="small-gap">
@@ -36,7 +41,7 @@ OSes can run x86-32 NaCl. If you try it out, please send us feedback
 on <a class="reference external" href="https://groups.google.com/forum/#!forum/native-client-dev">native-client-dev</a>. We are working on improvements and adding
 new targets.</li>
 </ul>
-<h3 id="pepper">Pepper</h3>
+<h3 id="id1">Pepper</h3>
 <ul class="small-gap">
 <li>UDP Socket Multicast API in development preview (PPB_UDP_SOCKET 1.2).</li>
 <li>Hardware Video Encoder API in development preview (PPB_VIDEO_ENCODER 0.1).</li>
@@ -55,7 +60,7 @@ can be used to generate NaCl <code>.nexe</code> files instead of translating a
 <li>The x86 NaCl validators accept instructions from the FMA3 extensions, as well
 as AVX2 instructions (except <code>VGATHER</code>).</li>
 </ul>
-<h3 id="id1">PNaCl</h3>
+<h3 id="id2">PNaCl</h3>
 <ul class="small-gap">
 <li>PNaCl supports C11/C++11 memory orders <code>acquire</code>, <code>release</code>, and
 <code>acq_rel</code>. It used to upgrade all accesses to <code>seq_cst</code>. It still upgrades
@@ -71,11 +76,11 @@ non-C languages such as Rust.</li>
 operations. This is often encountered when using large consecutive bitfields.</li>
 </ul>
 <h2 id="chrome-pepper-41-09-january-2015">Chrome/Pepper 41 (09 January 2015)</h2>
-<h3 id="id2">NaCl</h3>
+<h3 id="id3">NaCl</h3>
 <ul class="small-gap">
 <li>The x86 NaCl validators accept instructions from the AVX1 extensions.</li>
 </ul>
-<h3 id="id3">PNaCl</h3>
+<h3 id="id4">PNaCl</h3>
 <ul class="small-gap">
 <li>PNaCl is now based on LLVM 3.5.</li>
 </ul>
@@ -85,12 +90,12 @@ operations. This is often encountered when using large consecutive bitfields.</l
 stable, see the SDK example in <code>pepper_canary/examples/api/video_decode</code>.</li>
 </ul>
 <h2 id="chrome-pepper-39-26-september-2014">Chrome/Pepper 39 (26 September 2014)</h2>
-<h3 id="id4">NaCl</h3>
+<h3 id="id5">NaCl</h3>
 <ul class="small-gap">
 <li>This release contains a fix for CVE-2015-0565: <a class="reference external" href="https://code.google.com/p/nativeclient/issues/detail?id=3944">disable the x86 CLFLUSH
 instruction due to rowhammer problem</a>.</li>
 </ul>
-<h3 id="id5">Pepper</h3>
+<h3 id="id6">Pepper</h3>
 <ul class="small-gap">
 <li>Support for <code>DEBUG_ONLY:dev://postmessage</code> has been removed in favor of
 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#devcycle-debugging"><em>other more useful debugging approaches</em></a>.</li>
@@ -99,31 +104,31 @@ instruction due to rowhammer problem</a>.</li>
 embeds.</li>
 </ul>
 <h2 id="chrome-pepper-38-15-august-2014">Chrome/Pepper 38 (15 August 2014)</h2>
-<h3 id="id6">PNaCl</h3>
+<h3 id="id7">PNaCl</h3>
 <ul class="small-gap">
 <li>Compilation speed improvements due to validation caching of the translator and
 linker.</li>
 <li>Performance improvement of SIMD vector shuffle.</li>
 </ul>
 <h2 id="chrome-pepper-37-20-june-2014">Chrome/Pepper 37 (20 June 2014)</h2>
-<h3 id="id7">PNaCl</h3>
+<h3 id="id8">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="id8">Pepper</h3>
+<h3 id="id9">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="id9">SDK</h3>
+<h3 id="id10">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="id10">PNaCl</h3>
+<h3 id="id11">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
@@ -132,7 +137,7 @@ and performance is expected to become acceptable for version 37 of
 Chrome. More SIMD instructions will be added in later releases.</li>
 </ul>
 <h2 id="chrome-pepper-35-31-mar-2014">Chrome/Pepper 35 (31 Mar 2014)</h2>
-<h3 id="id11">PNaCl</h3>
+<h3 id="id12">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>
@@ -140,7 +145,7 @@ Chrome. More SIMD instructions will be added in later releases.</li>
 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>
 <h2 id="chrome-pepper-34-20-feb-2014">Chrome/Pepper 34 (20 Feb 2014)</h2>
-<h3 id="id12">Pepper</h3>
+<h3 id="id13">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
@@ -150,7 +155,7 @@ 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>
-<h3 id="id13">PNaCl</h3>
+<h3 id="id14">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
@@ -164,7 +169,7 @@ 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>
-<h3 id="id14">SDK</h3>
+<h3 id="id15">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
@@ -278,7 +283,7 @@ for an application can specify a source file to compile such as
 <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>
-<h3 id="id15">Build tools and toolchains</h3>
+<h3 id="id16">Build tools and toolchains</h3>
 <ul class="small-gap">
 <li><p class="first">Makefiles have been changed significantly:</p>
 <ul class="small-gap">
@@ -298,14 +303,14 @@ 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>
-<h3 id="id16">Libraries</h3>
+<h3 id="id17">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>
-<h3 id="id17">Examples</h3>
+<h3 id="id18">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>
@@ -327,7 +332,7 @@ 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>
-<h3 id="id18">Build tools and toolchains</h3>
+<h3 id="id19">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>
@@ -364,7 +369,7 @@ 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>
-<h3 id="id19">Libraries</h3>
+<h3 id="id20">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
@@ -398,7 +403,7 @@ 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>
-<h3 id="id20">Examples</h3>
+<h3 id="id21">Examples</h3>
 <ul class="small-gap">
 <li><p class="first">The SDK includes two new examples:</p>
 <ul class="small-gap">
@@ -439,7 +444,7 @@ source dependencies, and invokes the build rules in a separate file
 for &#8220;Portable Native Client&#8221;), 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>
-<h3 id="id21">Build tools and toolchains</h3>
+<h3 id="id22">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
 &#8220;pinnacle&#8221;). The PNaCl toolchain produces architecture-independent executable
@@ -455,7 +460,7 @@ 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>
-<h3 id="id23">Examples</h3>
+<h3 id="id24">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
@@ -466,7 +471,7 @@ 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>
-<h3 id="id24">PPAPI</h3>
+<h3 id="id25">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
@@ -538,7 +543,7 @@ Note that you must set the <code>CHROME_PATH</code> environment variable and sta
 </ul>
 </li>
 </ul>
-<h3 id="id25">Examples</h3>
+<h3 id="id26">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
@@ -554,7 +559,7 @@ onclick=&quot;...&quot;&gt;</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>
-<h3 id="id26">PPAPI</h3>
+<h3 id="id27">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>
@@ -565,14 +570,14 @@ been fixed.</li>
 <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>
-<h3 id="id27">Tools</h3>
+<h3 id="id28">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>
-<h3 id="id28">Windows SDK</h3>
+<h3 id="id29">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 &#8220;trusted&#8221; or &#8220;in-process&#8221; plugin) using the
@@ -620,7 +625,7 @@ 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>
-<h3 id="id29">Examples</h3>
+<h3 id="id30">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
@@ -634,7 +639,7 @@ in each example&#8217;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>
-<h3 id="id30">PPAPI</h3>
+<h3 id="id31">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
diff --git a/native_client_sdk/doc_generated/sitemap.html b/native_client_sdk/doc_generated/sitemap.html
index 53eba14..129b64c 100644
--- a/native_client_sdk/doc_generated/sitemap.html
+++ b/native_client_sdk/doc_generated/sitemap.html
@@ -42,6 +42,7 @@
 </ul>
 </li>
 <li class="toctree-l1"><a class="reference internal" href="/native-client/sdk/release-notes.html">Release Notes</a><ul class="small-gap">
+<li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-45-10-july-2015">Chrome/Pepper 45 (10 July 2015)</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-43-03-april-2015">Chrome/Pepper 43 (03 April 2015)</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-42-20-february-2015">Chrome/Pepper 42 (20 February 2015)</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-41-09-january-2015">Chrome/Pepper 41 (09 January 2015)</a></li>