summaryrefslogtreecommitdiffstats
path: root/native_client_sdk/src
diff options
context:
space:
mode:
authorjfb <jfb@chromium.org>2015-03-02 18:49:41 -0800
committerCommit bot <commit-bot@chromium.org>2015-03-03 02:50:51 +0000
commitcff96b94bca1ded99038abd5c744bc075f2532bb (patch)
treeb52e897405d1c00f287e2a2cb81c372b7e8daa8e /native_client_sdk/src
parentd52d3afcec84f7e15692971de4b9f31bc236c594 (diff)
downloadchromium_src-cff96b94bca1ded99038abd5c744bc075f2532bb.zip
chromium_src-cff96b94bca1ded99038abd5c744bc075f2532bb.tar.gz
chromium_src-cff96b94bca1ded99038abd5c744bc075f2532bb.tar.bz2
NaCl docs: acquire/release/acq_rel C++11 memory order in Chrome 43 SDK
R= bradnelson@chromium.org BUG= none Review URL: https://codereview.chromium.org/971493004 Cr-Commit-Position: refs/heads/master@{#318820}
Diffstat (limited to 'native_client_sdk/src')
-rw-r--r--native_client_sdk/src/doc/sdk/release-notes.rst34
1 files changed, 17 insertions, 17 deletions
diff --git a/native_client_sdk/src/doc/sdk/release-notes.rst b/native_client_sdk/src/doc/sdk/release-notes.rst
index f3ccf15..06eb857 100644
--- a/native_client_sdk/src/doc/sdk/release-notes.rst
+++ b/native_client_sdk/src/doc/sdk/release-notes.rst
@@ -8,15 +8,15 @@ 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.
-.. Chrome/Pepper 43 (03 April 2015)
-.. ===================================
-..
-.. PNaCl
-.. -----
-..
-.. * The C11/C++11 `acquire`, `release`, and `acq_rel` memory orders are now
- generated by default. The in-browser Chrome 42 translator supports them, the
- SDK can therefore generate them.
+Chrome/Pepper 43 (03 April 2015)
+================================
+
+PNaCl
+-----
+
+* The C11/C++11 ``acquire``, ``release``, and ``acq_rel`` memory orders are now
+ generated by default. The in-browser Chrome 42 translator supports them, the
+ SDK can therefore generate them.
Chrome/Pepper 42 (20 February 2015)
===================================
@@ -34,18 +34,18 @@ NaCl
----
* The x86 NaCl validators accept instructions from the FMA3 extensions, as well
- as AVX2 instructions (except `VGATHER`).
+ as AVX2 instructions (except ``VGATHER``).
PNaCl
-----
-* PNaCl supports C11/C++11 memory orders `acquire`, `release`, and `acq_rel`. It
- used to upgrade all accesses to `seq_cst`. It still upgrades `consume` to
- `acquire` (no compiler currently implements `consume`), and `relaxed` to
- `seq_cst` (to conservatively avoid platform differences due to out-of-thin-air
- problems). This is currently disabled by default in the SDK so that the
- in-browser translator installed on users' machines has time to gain this
- support. Developers can turn it on by passing the
+* PNaCl supports C11/C++11 memory orders ``acquire``, ``release``, and
+ ``acq_rel``. It used to upgrade all accesses to ``seq_cst``. It still upgrades
+ ``consume`` to ``acquire`` (no compiler currently implements ``consume``), and
+ ``relaxed`` to ``seq_cst`` (to conservatively avoid platform differences due
+ to out-of-thin-air problems). This is currently disabled by default in the SDK
+ so that the in-browser translator installed on users' machines has time to
+ gain this support. Developers can turn it on by passing the
``-pnacl-memory-order-seq-cst-only=false`` flag to ``opt``.
* PNaCl handles nested struct type expansion, which allows it to better support
non-C languages such as Rust.