[llvm-commits] [llvm] r55638 - /llvm/trunk/include/llvm/Function.h

[Devang Patel]

On Sep 24, 2008, at 12:11 PM, Duncan Sands wrote:

>> The pass that updates readonly and readone status can look at call
>> llvm.log parameters and do the right thing.
>
> Not if there are several calls to it with different parameters,
> which may be the case with link time optimization.

Would it be possible for you to give an example here ? Thx.

>  Also, this
> is a general mechanism - imagine it being used not for an llvm
> intrinsic but for a routine from a runtime library; then llvm
> wouldn't know about the special properties of the function.  But
> that's ok, it doesn't have to!

Sorry for being dense. I do not understand.
If I am using a library function F then I want the optimizer to know  
whether F is readonly or not. I do not care whether llvm.log() called  
by F is readonly or not.

-
Devang