Displaying 5 results from an estimated 5 matches for "pointeraccessinfo".
2009 Nov 06
0
[LLVMdev] Functions: sret and readnone
...etAnalysisUsage(llvm::AnalysisUsage &usage) const
{
AliasAnalysis::getAnalysisUsage(usage);
usage.setPreservesAll();
}
bool runOnFunction(Function &F)
{
AliasAnalysis::InitializeAliasAnalysis(this);
return false;
}
ModRefBehavior getModRefBehavior(CallSite CS,
std::vector<PointerAccessInfo> *Info = 0)
{
if(_srets.find(CS.getCalledFunction()->getName()) != _srets.end())
return AliasAnalysis::AccessesArguments; // only accesses args, no
globals
return AliasAnalysis::getModRefBehavior(CS, Info);
}
ModRefBehavior getModRefBehavior(Function *F,
std::vector<PointerAcces...
2009 Nov 06
2
[LLVMdev] Functions: sret and readnone
Hi Stephan,
> intrinsic float4 sample(int tex, float2 tc);
>
> float4 main(int tex, float2 tc)
> {
> float4 x = sample(tex, tc);
> return 0.0;
> }
without additional information it would be wrong to remove the call to
sample because it might write to a global variable.
> As you can see, the call to the sample function is still present,
> although the actual value
2009 Apr 18
0
[LLVMdev] GlobalsModRef
Hi,
In my pass, I want to use the alias-analysis info provided by "GlobalsModRef".
How should I use "getModRefBehavior(...)"-method and "alias(...)", in order to get the best presicion?
More precisely, how can I find the required arguments, particularly "PointerAccessInfo", for this methods. And is it a good idea to use "GlobalsModRef" in the "doInitialization" of a function-pass? Or it should be at best be used in a "runonModule" of a module-pass ?
many thanks in advance
Raad
-------------- next part --------------
An...
2007 Feb 22
0
[LLVMdev] Unused malloc/free don't get optimized
On Feb 22, 2007, at 1:54 PM, Nick Lewycky wrote:
> Vikram S. Adve wrote:
>> On Feb 22, 2007, at 10:21 AM, Robert L. Bocchino Jr. wrote:
>>
>>
>>> I glanced at the code again, and it looks like I use DSA to (1)
>>> construct the call graph and (2) identify things that would be
>>> unsafe to put on the stack, such as arrays, cyclic data structures,
2007 Feb 22
2
[LLVMdev] Unused malloc/free don't get optimized
Vikram S. Adve wrote:
> On Feb 22, 2007, at 10:21 AM, Robert L. Bocchino Jr. wrote:
>
>
>>I glanced at the code again, and it looks like I use DSA to (1)
>>construct the call graph and (2) identify things that would be
>>unsafe to put on the stack, such as arrays, cyclic data structures,
>>and allocations with escaping references. Right now these parts