OLD | NEW |
---|---|
1 .. _sdk-release-notes: | 1 .. _sdk-release-notes: |
2 | 2 |
3 ############# | 3 ############# |
4 Release Notes | 4 Release Notes |
5 ############# | 5 ############# |
6 | 6 |
7 The dates in the following release notes denote when Chrome and the NaCl SDK | 7 The dates in the following release notes denote when Chrome and the NaCl SDK |
8 reached canary status. The stable release is typically 6 weeks later. | 8 reached canary status. The stable release is typically 6 weeks later. |
9 | 9 |
10 | 10 |
11 Chrome/Pepper 43 (03 April 2015) | 11 Chrome/Pepper 43 (03 April 2015) |
12 ================================ | 12 ================================ |
13 | 13 |
14 PNaCl | 14 PNaCl |
15 ----- | 15 ----- |
16 | 16 |
17 * The C11/C++11 ``acquire``, ``release``, and ``acq_rel`` memory orders are now | 17 * The C11/C++11 ``acquire``, ``release``, and ``acq_rel`` memory orders are now |
18 generated by default. The in-browser Chrome 42 translator supports them, the | 18 generated by default. The in-browser Chrome 42 translator supports them, the |
19 SDK can therefore generate them. | 19 SDK can therefore generate them. |
20 * Fix a `code generation bug on ARM`_ when dealing with 16-bit load/store and | 20 * Fix a `code generation bug on ARM`_ when dealing with 16-bit load/store and |
21 ``bswap`` which led to a NaCl validation failure. | 21 ``bswap`` which led to a NaCl validation failure. |
22 * PNaCl is now based on LLVM 3.6. If you are using GDB to debug PNaCl | |
23 :ref:`BC files with debug metadata in the browser<debugging_pnacl_pexes>`, | |
24 remember that the SDK version must match the in-browser translator version. | |
binji
2015/04/01 16:59:00
how can the developer know that the SDK version ma
jvoung (off chromium)
2015/04/01 17:22:56
Reworded to say use SDK version X for chrome versi
| |
25 Bitcode debug metadata changed from LLVM 3.5 to 3.6. Otherwise, it is still | |
binji
2015/04/01 16:59:00
"Otherwise" sounds weird here. Otherwise what?
jvoung (off chromium)
2015/04/01 17:22:56
Reworded -- is this better?
| |
26 possible to work around this version-match issue by translating pexes to | |
27 nexes using the :ref:`offline translator in the same SDK | |
28 <debugging_pexes_via_nexes>` instead of using the translator in | |
29 the browser. | |
22 | 30 |
23 .. _`code generation bug on ARM`: https://code.google.com/p/chromium/issues/deta il?id=460432 | 31 .. _`code generation bug on ARM`: https://code.google.com/p/chromium/issues/deta il?id=460432 |
24 | 32 |
25 Chrome/Pepper 42 (20 February 2015) | 33 Chrome/Pepper 42 (20 February 2015) |
26 =================================== | 34 =================================== |
27 | 35 |
28 SDK | 36 SDK |
29 --- | 37 --- |
30 | 38 |
31 * The SDK now contains experimental versions of ``i686-nacl-clang``, | 39 * The SDK now contains experimental versions of ``i686-nacl-clang``, |
(...skipping 680 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
712 | 720 |
713 PPAPI | 721 PPAPI |
714 ----- | 722 ----- |
715 | 723 |
716 * The ``CompletionCallbackFactory`` class template now takes a thread traits | 724 * The ``CompletionCallbackFactory`` class template now takes a thread traits |
717 class as its second parameter. For details see the `CompletionCallbackFactory | 725 class as its second parameter. For details see the `CompletionCallbackFactory |
718 class template reference | 726 class template reference |
719 </native-client/pepper_stable/cpp/classpp_1_1_completion_callback_factory#deta ils>`_. | 727 </native-client/pepper_stable/cpp/classpp_1_1_completion_callback_factory#deta ils>`_. |
720 | 728 |
721 .. TODO: Port release notes for older releases | 729 .. TODO: Port release notes for older releases |
OLD | NEW |