[llvm-branch-commits] [llvm-branch] r229874 - Add release notes about vectorcall support and Win64 unwind info

[Reid Kleckner]

Author: rnk
Date: Thu Feb 19 11:51:19 2015
New Revision: 229874

URL: http://llvm.org/viewvc/llvm-project?rev=229874&view=rev
Log:
Add release notes about vectorcall support and Win64 unwind info

Modified:
    llvm/branches/release_36/docs/ReleaseNotes.rst

Modified: llvm/branches/release_36/docs/ReleaseNotes.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/branches/release_36/docs/ReleaseNotes.rst?rev=229874&r1=229873&r2=229874&view=diff
==============================================================================
--- llvm/branches/release_36/docs/ReleaseNotes.rst (original)
+++ llvm/branches/release_36/docs/ReleaseNotes.rst Thu Feb 19 11:51:19 2015
@@ -37,6 +37,9 @@ Non-comprehensive list of changes in thi
 * Added support for a `native object file-based bitcode wrapper format
   <BitCodeFormat.html#native-object-file>`_.
 
+* Added support for MSVC's ``__vectorcall`` calling convention as
+  ``x86_vectorcallcc``.
+
 * ... next change ...
 
 .. NOTE
@@ -354,9 +357,20 @@ The syntax of comdats was changed to
 The version without the parentheses is a syntatic sugar for a comdat with
 the same name as the global.
 
+Added support for Win64 unwind information
+------------------------------------------
+
+LLVM now obeys the `Win64 prologue and epilogue conventions
+<https://msdn.microsoft.com/en-us/library/tawsa7cb.aspx>`_ documented by
+Microsoft. Unwind information is also emitted into the .xdata section.
+
+As a result of the ABI-required prologue changes, it is now no longer possible
+to unwind the stack using a standard frame pointer walk on Win64. Instead,
+users should call ``CaptureStackBackTrace``, or implement equivalent
+functionality by consulting the unwind tables present in the binary.
 
-Diagnotic infrastructure used by lib/Linker and lib/Bitcode
------------------------------------------------------------
+Diagnostic infrastructure used by lib/Linker and lib/Bitcode
+------------------------------------------------------------
 
 These libraries now use the diagnostic handler to print errors and warnings.
 This provides better error messages and simpler error handling.