From 9d78bbe6c4a9026228dd11744e6a43d7ab5677d8 Mon Sep 17 00:00:00 2001 From: Mindong Chen Date: Mon, 14 Nov 2022 23:18:47 +0800 Subject: [PATCH] [docs][OpaquePtr] Fix hyperlinks --- llvm/docs/OpaquePointers.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/llvm/docs/OpaquePointers.rst b/llvm/docs/OpaquePointers.rst index 5d0e7ae..7573de6 100644 --- a/llvm/docs/OpaquePointers.rst +++ b/llvm/docs/OpaquePointers.rst @@ -56,7 +56,7 @@ more of a hindrance for LLVM development and that the extra type checking with some frontends wasn't worth it. LLVM's type system was `originally designed -` to support high-level +`_ to support high-level optimization. However, years of LLVM implementation experience have demonstrated that the pointee type system design does not effectively support optimization. Memory optimization algorithms, such as SROA, GVN, and AA, @@ -64,7 +64,7 @@ generally need to look through LLVM's struct types and reason about the underlying memory offsets. The community realized that pointee types hinder LLVM development, rather than helping it. Some of the initially proposed high-level optimizations have evolved into `TBAA -` due to limitations with +`_ due to limitations with representing higher-level language information directly via SSA values. Pointee types provide some value to frontends because the IR verifier uses types -- 2.7.4