aboutsummaryrefslogtreecommitdiff
path: root/mlir/docs/PassManagement.md
diff options
context:
space:
mode:
Diffstat (limited to 'mlir/docs/PassManagement.md')
-rw-r--r--mlir/docs/PassManagement.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/mlir/docs/PassManagement.md b/mlir/docs/PassManagement.md
index ff86bbf..c9d705f 100644
--- a/mlir/docs/PassManagement.md
+++ b/mlir/docs/PassManagement.md
@@ -56,8 +56,7 @@ By default, an operation pass is `op-agnostic`, meaning that it operates on the
operation type of the pass manager that it is added to. This means a pass may operate
on many different types of operations. Agnostic passes should be written such that
they do not make assumptions on the operation they run on. Examples of this type of pass are
-[Canonicalization](Pass.md/-canonicalize-canonicalize-operations)
-[Common Sub-Expression Elimination](Passes.md/#-cse-eliminate-common-sub-expressions).
+[Canonicalization](Passes.md/#-canonicalize) and [Common Sub-Expression Elimination](Passes.md/#-cse).
To create an agnostic operation pass, a derived class must adhere to the following: