From 8c0e62cdb274635d9f92c22836a80ea3d5e937cc Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Mon, 9 Mar 2009 20:55:18 +0000 Subject: [PATCH] Clarify wording, patch by Stefanus Du Toit! git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@66458 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.html | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/LangRef.html b/docs/LangRef.html index 0985cbd61e6..6b7038dbccb 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -3637,11 +3637,13 @@ the LLVM code for the given testcase is equivalent to:

} -

Note that it is undefined to access an array out of bounds: array and -pointer indexes must always be within the defined bounds of the array type. -The one exception for this rule is zero length arrays. These arrays are -defined to be accessible as variable length arrays, which requires access -beyond the zero'th element.

+

Note that it is undefined to access an array out of bounds: array +and pointer indexes must always be within the defined bounds of the +array type when accessed with an instruction that dereferences the +pointer (e.g. a load or store instruction). The one exception for +this rule is zero length arrays. These arrays are defined to be +accessible as variable length arrays, which requires access beyond the +zero'th element.

The getelementptr instruction is often confusing. For some more insight into how it works, see the getelementptr -- 2.34.1