From e53e508642c5bd95c9dcb64203e18c0c520c77e6 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Thu, 3 Jun 2004 22:57:15 +0000 Subject: [PATCH] Fix some broken links git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@13997 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/LangRef.html b/docs/LangRef.html index 07bb686698b..3421b3d4bd0 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -522,7 +522,7 @@ instruction.

{ float, int (int) * } : A pair, where the first element is a float and the second element is a pointer to a function that takes an int, returning + href="#t_function">function that takes an int, returning an int. @@ -549,7 +549,7 @@ of four int values int (int *) * : A pointer to a function that takes an int, returning + href="#t_function">function that takes an int, returning an int. @@ -1417,7 +1417,7 @@ Instruction
Arguments:

The argument to the 'load' instruction specifies the memory address to load from. The pointer must point to a first class type. If the load is + href="#t_firstclass">first class type. If the load is marked as volatile then the optimizer is not allowed to modify the number or order of execution of this load with other volatile load and store @@ -1519,9 +1519,9 @@ compiled to LLVM:

Semantics:

The index types specified for the 'getelementptr' instruction depend -on the pointer type that is being index into. Pointer -and array types require uint, int, -ulong, or long values, and structure +on the pointer type that is being index into. Pointer +and array types require uint, int, +ulong, or long values, and structure types require uint constants.

In the example above, the first index is indexing into the '%ST*'