From 19527c6ef371c6a09743bf91d4bee36b32241b12 Mon Sep 17 00:00:00 2001 From: Duncan Sands Date: Sun, 22 Mar 2009 11:33:16 +0000 Subject: [PATCH] Add some explanations of how apint loads and stores work. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@67471 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.html | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/docs/LangRef.html b/docs/LangRef.html index 94f3c3d75a8..cac8fc79dad 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -3486,7 +3486,13 @@ alignment may produce less efficient code. An alignment of 1 is always safe.

Semantics:
-

The location of memory pointed to is loaded.

+

The location of memory pointed to is loaded. If the value being loaded +is of scalar type then the number of bytes read does not exceed the minimum +number of bytes needed to hold all bits of the type. For example, loading an +i24 reads at most three bytes. When loading a value of a type like +i20 with a size that is not an integral number of bytes, the result +is undefined if the value was not originally written using a store of the +same type.

Examples:
  %ptr = alloca i32                               ; yields {i32*}:ptr
   
 
Semantics:

 
The contents of memory are updated to contain '<value>'
-at the location specified by the '<pointer>' operand.

+at the location specified by the '<pointer>' operand.
+If '<value>' is of scalar type then the number of bytes
+written does not exceed the minimum number of bytes needed to hold all
+bits of the type.  For example, storing an i24 writes at most
+three bytes.  When writing a value of a type like i20 with a
+size that is not an integral number of bytes, it is unspecified what
+happens to the extra bits that do not belong to the type, but they will
+typically be overwritten.

 
Example:

 
  %ptr = alloca i32                               ; yields {i32*}:ptr
   store i32 3, i32* %ptr                          ; yields {void}