Correct a comment: since AccessArguments is now

being used for atomic intrinsics, it seems the
access may be volatile.  No code was exploiting
the original non-volatile definition, so only
the comment needs changing.

llvm-svn: 64464
This commit is contained in:
Duncan Sands 2009-02-13 17:36:13 +00:00
parent 566ed10244
commit a738e8b854
1 changed files with 3 additions and 3 deletions

View File

@ -126,15 +126,15 @@ public:
// This property corresponds to the GCC 'const' attribute.
DoesNotAccessMemory,
// AccessesArguments - This function accesses function arguments in
// non-volatile and well known ways, but does not access any other memory.
// AccessesArguments - This function accesses function arguments in well
// known (possibly volatile) ways, but does not access any other memory.
//
// Clients may use the Info parameter of getModRefBehavior to get specific
// information about how pointer arguments are used.
AccessesArguments,
// AccessesArgumentsAndGlobals - This function has accesses function
// arguments and global variables in non-volatile and well-known ways, but
// arguments and global variables well known (possibly volatile) ways, but
// does not access any other memory.
//
// Clients may use the Info parameter of getModRefBehavior to get specific