[llvm] 3806d88 - [docs][NewPM] Clarify more status of legacy PM + optimization pipeline

[Arthur Eubanks via llvm-commits]

Author: Arthur Eubanks
Date: 2023-01-16T17:42:08-08:00
New Revision: 3806d885ae2d6f49601e8a4af69e779d474b5326

URL: https://github.com/llvm/llvm-project/commit/3806d885ae2d6f49601e8a4af69e779d474b5326
DIFF: https://github.com/llvm/llvm-project/commit/3806d885ae2d6f49601e8a4af69e779d474b5326.diff

LOG: [docs][NewPM] Clarify more status of legacy PM + optimization pipeline

Reviewed By: asbirlea, nikic

Differential Revision: https://reviews.llvm.org/D141443

Added: 
    

Modified: 
    llvm/docs/NewPassManager.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/NewPassManager.rst b/llvm/docs/NewPassManager.rst
index cf464803345d..a9fa72cf6eb8 100644
--- a/llvm/docs/NewPassManager.rst
+++ b/llvm/docs/NewPassManager.rst
@@ -506,13 +506,11 @@ Status of the New and Legacy Pass Managers
 ==========================================
 
 LLVM currently contains two pass managers, the legacy PM and the new PM. The
-optimization pipeline (aka the middle-end) works with both the legacy PM and
-the new PM, whereas the backend target-dependent code generation only works
-with the legacy PM.
+optimization pipeline (aka the middle-end) uses the new PM, whereas the backend
+target-dependent code generation uses the legacy PM.
 
-For the optimization pipeline, the new PM is the default PM. Using the legacy PM
-for the optimization pipeline is deprecated and there are ongoing efforts to
-remove its usage.
+The legacy PM somewhat works with the optimization pipeline, but this is
+deprecated and there are ongoing efforts to remove its usage.
 
 Some IR passes are considered part of the backend codegen pipeline even if
 they are LLVM IR passes (whereas all MIR passes are codegen passes). This