From: Chris Lattner Date: Sun, 3 May 2009 18:49:37 +0000 (+0000) Subject: be very explicit that readnone/readonly functions can't X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=7a57c5bb080e7046e78380cde36f648e888912d7;p=oota-llvm.git be very explicit that readnone/readonly functions can't throw exceptions. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@70788 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/LangRef.html b/docs/LangRef.html index be8ff733318..1a9567a2b39 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -1066,7 +1066,8 @@ exception it throws) based strictly on its arguments, without dereferencing any pointer arguments or otherwise accessing any mutable state (e.g. memory, control registers, etc) visible to caller functions. It does not write through any pointer arguments (including byval arguments) and -never changes any state visible to callers. +never changes any state visible to callers. readnone functions may not throw +an exception that escapes into the caller.
readonly
This attribute indicates that the function does not write through any @@ -1075,7 +1076,8 @@ or otherwise modify any state (e.g. memory, control registers, etc) visible to caller functions. It may dereference pointer arguments and read state that may be set in the caller. A readonly function always returns the same value (or throws the same exception) when called with the same set of arguments and global -state.
+state. readonly functions may not throw an exception that escapes into the +caller.
ssp
This attribute indicates that the function should emit a stack smashing