summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorEric Christopher <echristo@apple.com>2009-12-01 22:28:41 +0000
committerEric Christopher <echristo@apple.com>2009-12-01 22:28:41 +0000
commit8aa46bc6fdf210b30dc2c63db3b06cd9c5062951 (patch)
tree054fec937768c2d8fe5e8001bcff18ac0adb1f50 /llvm/docs
parenta6d407c29604dc7913af8441c5eb2ffd477c20af (diff)
downloadbcm5719-llvm-8aa46bc6fdf210b30dc2c63db3b06cd9c5062951.tar.gz
bcm5719-llvm-8aa46bc6fdf210b30dc2c63db3b06cd9c5062951.zip
Update per Bill's comments. Work in progress.
llvm-svn: 90271
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/LangRef.html16
1 files changed, 8 insertions, 8 deletions
diff --git a/llvm/docs/LangRef.html b/llvm/docs/LangRef.html
index 5eeea6452e3..691e34171fc 100644
--- a/llvm/docs/LangRef.html
+++ b/llvm/docs/LangRef.html
@@ -7263,22 +7263,22 @@ LLVM</a>.</p>
<h5>Overview:</h5>
<p>The <tt>llvm.objectsize</tt> intrinsic returns the constant number of bytes
- from <tt>ptr</tt> to the end of the object <tt>ptr</tt> points to if it
+ from <tt>ptr</tt> to the end of the object <tt>ptr</tt> points to, if it
can deduce this at compile time. If there are any side-effects in evaluating
the argument or it cannot deduce which objects <tt>ptr</tt> points to at compile
- time the intrinsic returns <tt>(size_t) -1</tt> for <tt>type</tt> 0
- or 1 and <tt>(size_t) 0</tt> for <tt>type</tt> 2 or 3.</p>
+ time, the intrinsic returns <tt>i32/i64 -1</tt> for <tt>type</tt> 0
+ or 1 and <tt>i32/i64 0</tt> for <tt>type</tt> 2 or 3.</p>
<h5>Arguments:</h5>
<p>The <tt>llvm.objectsize</tt> intrinsic takes two arguments. The first
- argument is a pointer to the object <tt>ptr</tt> and an integer <tt>type</tt>.
- <tt>type</tt> is an integer ranging from 0 to 3. The lsb corresponds to
- a return value based on whole objects, the second bit whether or not we
- return the maximum or minimum remaining bytes computed.</p>
+ argument is a pointer to the object <tt>ptr</tt>. The second argument
+ is an integer <tt>type</tt> which ranges from 0 to 3. The first bit
+ corresponds to a return value based on whole objects, and the second bit
+ whether or not we return the maximum or minimum remaining bytes computed.</p>
<h5>Semantics:</h5>
<p>The <tt>llvm.objectsize</tt> intrinsic is lowered to either a constant
- representing the size of the object concerned or <tt>(size_t) -1</tt> if
+ representing the size of the object concerned or <tt>i32/i64 -1</tt> if
it cannot be determined at compile time.</p>
</div>
OpenPOWER on IntegriCloud