Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(11)

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

Issue 1051653004: Add NaCl SDK release note about LLVM 3.6 and debug metadata changes. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: line wrap Created 5 years, 9 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
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..a0dbcdd446046e56d4bb1ce186a60a33859fd854 100644
--- a/native_client_sdk/doc_generated/sdk/release-notes.html
+++ b/native_client_sdk/doc_generated/sdk/release-notes.html
@@ -12,6 +12,13 @@ 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 the SDK version must match the in-browser translator version.
+Bitcode debug metadata changed from LLVM 3.5 to 3.6. Otherwise, it is still
+possible to work around this version-match issue by translating pexes to
+nexes using the <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html#debugging-pexes-via-nexes"><em>offline translator in the same SDK</em></a> instead of using the translator in
+the browser.</li>
</ul>
<h2 id="chrome-pepper-42-20-february-2015">Chrome/Pepper 42 (20 February 2015)</h2>
<h3 id="sdk">SDK</h3>

Powered by Google App Engine
This is Rietveld 408576698