From 7533ac180c4757163d6420f3fc2dd7b619f2085c Mon Sep 17 00:00:00 2001 From: George Burgess IV Date: Sun, 21 May 2017 05:31:29 +0000 Subject: [PATCH] [Docs] Fix LangRef links referred in GetElementPtr.rst Patch by chenwj! Differential Revision: https://reviews.llvm.org/D32929 llvm-svn: 303499 --- llvm/docs/GetElementPtr.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/llvm/docs/GetElementPtr.rst b/llvm/docs/GetElementPtr.rst index f39f1d9207a2..d13479dabca8 100644 --- a/llvm/docs/GetElementPtr.rst +++ b/llvm/docs/GetElementPtr.rst @@ -9,10 +9,11 @@ Introduction ============ This document seeks to dispel the mystery and confusion surrounding LLVM's -`GetElementPtr `_ (GEP) instruction. Questions -about the wily GEP instruction are probably the most frequently occurring -questions once a developer gets down to coding with LLVM. Here we lay out the -sources of confusion and show that the GEP instruction is really quite simple. +`GetElementPtr `_ (GEP) instruction. +Questions about the wily GEP instruction are probably the most frequently +occurring questions once a developer gets down to coding with LLVM. Here we lay +out the sources of confusion and show that the GEP instruction is really quite +simple. Address Computation =================== @@ -429,7 +430,8 @@ because LLVM has no restrictions on mixing types in addressing, loads or stores. LLVM's type-based alias analysis pass uses metadata to describe a different type system (such as the C type system), and performs type-based aliasing on top of -that. Further details are in the `language reference `_. +that. Further details are in the +`language reference `_. What happens if a GEP computation overflows? --------------------------------------------