Displaying 5 results from an estimated 5 matches for "vncoercion".
Did you mean:
coercion
2017 Jul 16
4
PartialAlias: different start addresses
...>> ./Scalar/DeadStoreElimination.cpp
> >> ./Scalar/GVN.cpp
> >> ./Scalar/LICM.cpp
> >> ./Scalar/LoopVersioningLICM.cpp
> >> ./Scalar/MemCpyOptimizer.cpp
> >> ./Scalar/MergedLoadStoreMotion.cpp
> >> ./Scalar/NewGVN.cpp
> >> ./Utils/VNCoercion.cpp
> >>
> >> I glanced over all the uses in these files and I couldn't find any
> >> usage that requires sizes to match. Actually most clients check
> >> access sizes themselves. Most don't need equal sizes, just need one to
> >> be smaller tha...
2017 Jul 15
2
PartialAlias: different start addresses
...; ./ObjCARC/ProvenanceAnalysis.cpp
>> ./Scalar/DeadStoreElimination.cpp
>> ./Scalar/GVN.cpp
>> ./Scalar/LICM.cpp
>> ./Scalar/LoopVersioningLICM.cpp
>> ./Scalar/MemCpyOptimizer.cpp
>> ./Scalar/MergedLoadStoreMotion.cpp
>> ./Scalar/NewGVN.cpp
>> ./Utils/VNCoercion.cpp
>>
>> I glanced over all the uses in these files and I couldn't find any usage
>> that requires sizes to match. Actually most clients check access sizes
>> themselves. Most don't need equal sizes, just need one to be smaller than
>> the other.
>>
>...
2017 Jul 15
2
PartialAlias: different start addresses
...s:
~/llvm/lib/Transforms $ grep -Rl MustAlias .
./ObjCARC/ObjCARCOpts.cpp
./ObjCARC/ProvenanceAnalysis.cpp
./Scalar/DeadStoreElimination.cpp
./Scalar/GVN.cpp
./Scalar/LICM.cpp
./Scalar/LoopVersioningLICM.cpp
./Scalar/MemCpyOptimizer.cpp
./Scalar/MergedLoadStoreMotion.cpp
./Scalar/NewGVN.cpp
./Utils/VNCoercion.cpp
I glanced over all the uses in these files and I couldn't find any usage
that requires sizes to match. Actually most clients check access sizes
themselves. Most don't need equal sizes, just need one to be smaller than
the other.
BTW, Basic AA doesn't check for size either:
if...
2017 Jul 16
2
PartialAlias: different start addresses
...t;>>> ./Scalar/GVN.cpp
>>>>> ./Scalar/LICM.cpp
>>>>> ./Scalar/LoopVersioningLICM.cpp
>>>>> ./Scalar/MemCpyOptimizer.cpp
>>>>> ./Scalar/MergedLoadStoreMotion.cpp
>>>>> ./Scalar/NewGVN.cpp
>>>>> ./Utils/VNCoercion.cpp
>>>>>
>>>>> I glanced over all the uses in these files and I couldn't find any
>>>>> usage that requires sizes to match. Actually most clients check
>>>>> access sizes themselves. Most don't need equal sizes, just need one to...
2017 Jul 14
2
PartialAlias: different start addresses
Thank you all for your replies.
So here seems to be an agreement that the documentation for PartialAlias is
incorrect.
Daniel: now you got me wondering about MustAlias. This is what the docs say:
"The MustAlias response may only be returned if the two memory objects are
*guaranteed to always start at exactly the same location*"
This statement is regardless of the access sizes. For