svn commit: r345142 - vendor/llvm/dist-release_80/docs

[Dimitry Andric]

Author: dim
Date: Thu Mar 14 19:41:10 2019
New Revision: 345142
URL: https://svnweb.freebsd.org/changeset/base/345142

Log:
  Vendor import of llvm release_80 branch r356034:
  https://llvm.org/svn/llvm-project/llvm/branches/release_80@356034

Modified:
  vendor/llvm/dist-release_80/docs/ReleaseNotes.rst

Modified: vendor/llvm/dist-release_80/docs/ReleaseNotes.rst
==============================================================================
--- vendor/llvm/dist-release_80/docs/ReleaseNotes.rst	Thu Mar 14 19:07:41 2019	(r345141)
+++ vendor/llvm/dist-release_80/docs/ReleaseNotes.rst	Thu Mar 14 19:41:10 2019	(r345142)
@@ -95,6 +95,22 @@ Changes to the LLVM IR
   <SpeculativeLoadHardening.html>`_ must be enabled for the function body.
 
 
+Changes to the JIT APIs
+-----------------------
+
+The ORC (On Request Compilation) JIT APIs have been updated to support
+concurrent compilation. The existing (non-concurrent) ORC layer classes and
+related APIs are deprecated, have been renamed with a "Legacy" prefix (e.g.
+LegacyIRCompileLayer). The deprecated clasess will be removed in LLVM 9.
+
+An example JIT stack using the concurrent ORC APIs, called LLJIT, has been
+added (see include/llvm/ExecutionEngine/Orc/LLJIT.h). The lli tool has been
+updated to use LLJIT.
+
+MCJIT and ExecutionEngine continue to be supported, though ORC should be
+preferred for new projects.
+
+
 Changes to the AArch64 Target
 -----------------------------
 
@@ -171,6 +187,26 @@ Changes to the PowerPC Target
 * Completed support in LLD for ELFv2
 
 * Enabled llvm-exegesis latency mode for PPC
+
+
+Changes to the SystemZ Target
+-----------------------------
+
+* A number of bugs related to C/C++ language vector extension support were
+  fixed: the ``-mzvector`` option now actually enables the ``__vector`` and
+  ``__bool`` keywords, the ``vec_step`` intrinsic now works, and the
+  ``vec_insert_and_zero`` and ``vec_orc`` intrinsics now generate correct code.
+
+* The ``__float128`` keyword, which had been accidentally enabled in some
+  earlier releases, is now no longer supported.  On SystemZ, the ``long double``
+  data type itself already uses the IEEE 128-bit floating-point format.
+
+* When the compiler inlines ``strcmp`` or ``memcmp``, the generated code no
+  longer returns ``INT_MIN`` as the negative result value under any
+  circumstances.
+
+* Various code-gen improvements, in particular related to improved
+  auto-vectorization, inlining, and instruction scheduling.
 
 
 Changes to the X86 Target