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 7ef7f665df89f80347bb0cd36dfd8ce2178682ff..20836b559f589f0033e18b511f6bd1d0a0d6ece9 100644 |
--- a/native_client_sdk/doc_generated/sdk/release-notes.html |
+++ b/native_client_sdk/doc_generated/sdk/release-notes.html |
@@ -12,6 +12,15 @@ generated by default. The in-browser Chrome 42 translator supports them, the |
SDK can therefore generate them.</li> |
<li>Fix a <a class="reference external" href="https://code.google.com/p/chromium/issues/detail?id=460432">code generation bug on ARM</a> when dealing with 16-bit load/store and |
<code>bswap</code> which led to a NaCl validation failure.</li> |
+<li>PNaCl is now based on LLVM 3.6. If you are using GDB to debug PNaCl |
+<a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#debugging-pnacl-pexes"><em>BC files with debug metadata in the browser</em></a>, |
+remember that debug info from SDK version <code>X</code> is only compatible with the |
+PNaCl translator in chrome version <code>X</code>. The bitcode debug metadata format |
+changed from LLVM 3.5 to 3.6. If you need to debug an app built with SDK |
+version <code>X</code> running in Chrome version <code>Y</code> (with <code>X != Y</code>), it is still |
+possible to do so. Simply translate the pexe to a nexe using the |
+<a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#debugging-pexes-via-nexes"><em>offline pnacl-translate tool from SDK version X</em></a> instead of using the translator in the |
+browser (version <code>Y</code>).</li> |
</ul> |
<h2 id="chrome-pepper-42-20-february-2015">Chrome/Pepper 42 (20 February 2015)</h2> |
<h3 id="sdk">SDK</h3> |