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

Reviewed By: asbirlea, nikic

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

diff --git a/llvm/docs/NewPassManager.rst b/llvm/docs/NewPassManager.rst
index cf46480..a9fa72c 100644 (file)
--- 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