Displaying 3 results from an estimated 3 matches for "maxlookup".
Did you mean:
map_lookup
2013 Feb 05
3
[LLVMdev] Vectorizing global struct pointers
...he value was already there, it's a conflict.
However, the read is from Foo.bl / Foo.cl and the write to Foo.al, so why
is GetUnderlyingObjects() returning the same objects/pointers?
A quick look at it revealed me the problem:
llvm::GetUnderlyingObject(Value *V, const DataLayout *TD, unsigned
MaxLookup) yields:
-> GEPOperator *GEP = dyn_cast<GEPOperator>(V)
-> V = GEP->getPointerOperand();
-> GlobalAlias *GA = dyn_cast<GlobalAlias>(V)
-> V = GA->getAliasee();
return V;
In this case, V is a reference to the structure, not the element. It seems
to me that assigning t...
2013 Feb 05
0
[LLVMdev] Vectorizing global struct pointers
...'s a conflict.
>
> However, the read is from Foo.bl / Foo.cl and the write to Foo.al, so why is GetUnderlyingObjects() returning the same objects/pointers?
>
> A quick look at it revealed me the problem:
>
> llvm::GetUnderlyingObject(Value *V, const DataLayout *TD, unsigned MaxLookup) yields:
>
> -> GEPOperator *GEP = dyn_cast<GEPOperator>(V)
> -> V = GEP->getPointerOperand();
> -> GlobalAlias *GA = dyn_cast<GlobalAlias>(V)
> -> V = GA->getAliasee();
> return V;
>
> In this case, V is a reference to the structure, not the...
2013 Feb 05
3
[LLVMdev] Vectorizing global struct pointers
...> > However, the read is from Foo.bl / Foo.cl and the write to Foo.al, so why is GetUnderlyingObjects() returning the same objects/pointers?
> >
> > A quick look at it revealed me the problem:
> >
> > llvm::GetUnderlyingObject(Value *V, const DataLayout *TD, unsigned MaxLookup) yields:
> >
> > -> GEPOperator *GEP = dyn_cast<GEPOperator>(V)
> > -> V = GEP->getPointerOperand();
> > -> GlobalAlias *GA = dyn_cast<GlobalAlias>(V)
> > -> V = GA->getAliasee();
> > return V;
> >
> > In this case, V i...