[llvm] r375045 - Update ReleaseNotes: expand the section on enabling MemorySSA

Alina Sbirlea via llvm-commits llvm-commits at lists.llvm.org
Wed Oct 16 14:52:09 PDT 2019


Author: asbirlea
Date: Wed Oct 16 14:52:09 2019
New Revision: 375045

URL: http://llvm.org/viewvc/llvm-project?rev=375045&view=rev
Log:
Update ReleaseNotes: expand the section on enabling MemorySSA

Modified:
    llvm/trunk/docs/ReleaseNotes.rst

Modified: llvm/trunk/docs/ReleaseNotes.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ReleaseNotes.rst?rev=375045&r1=375044&r2=375045&view=diff
==============================================================================
--- llvm/trunk/docs/ReleaseNotes.rst (original)
+++ llvm/trunk/docs/ReleaseNotes.rst Wed Oct 16 14:52:09 2019
@@ -41,7 +41,20 @@ Non-comprehensive list of changes in thi
    for adding a new subsection.
 
 * The ISD::FP_ROUND_INREG opcode and related code was removed from SelectionDAG.
-* Enabled MemorySSA as a loop dependency.
+* Enabled MemorySSA as a loop dependency. Since
+  `r370957 <https://reviews.llvm.org/rL370957>`_
+  (`D58311 <https://reviews.llvm.org/D58311>`_ ``[MemorySSA & LoopPassManager]
+  Enable MemorySSA as loop dependency. Update tests.``), the MemorySSA analysis
+  is being preserved and used by a series of loop passes. The most significant
+  use is in LICM, where the instruction hoisting and sinking relies on aliasing
+  information provided by MemorySSA vs previously creating an AliasSetTracker.
+  The LICM step of promoting variables to scalars still relies on the creation
+  of an AliasSetTracker, but its use is reduced to only be enabled for loops
+  with a small number of overall memory instructions. This choice was motivated
+  by experimental results showing compile and run time benefits or replacing the
+  AliasSetTracker usage with MemorySSA without any performance penalties.
+  The fact that MemorySSA is now preserved by and available in a series of loop
+  passes, also opens up opportunities for its use in those respective passes.
 
 .. NOTE
    If you would like to document a larger change, then you can add a




More information about the llvm-commits mailing list