From: Chris Lattner Date: Tue, 15 Jan 2008 04:34:22 +0000 (+0000) Subject: clarify that byval is valid for any pointer argument. X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=0747baaf6accc331d74764f965b9386e44374eeb;p=oota-llvm.git clarify that byval is valid for any pointer argument. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@45998 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LangRef.html b/docs/LangRef.html index fa5019370a4..49bcc974f08 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -810,11 +810,12 @@ declare i32 @atoi(i8*) nounwind readonly target-specific
byval
-
This indicates that the pointer parameter is really an aggregate that - was passed by value to the function. The attribute implies that a hidden - copy of the struct is made between the caller and the callee, so the - callee is unable to modify the struct in the callee. This attribute is only - valid on llvm pointer arguments.
+
This indicates that the pointer parameter should really be passed by + value to the function. The attribute implies that a hidden copy of the + pointee is made between the caller and the callee, so the callee is unable + to modify the value in the callee. This attribute is only valid on llvm + pointer arguments. It is generally used to pass structs and arrays by + value, but is also valid on scalars (even though this is silly).
sret
This indicates that the parameter specifies the address of a structure