Displaying 6 results from an estimated 6 matches for "phatom_mem".
2017 Sep 12
3
RFC phantom memory intrinsic
...particular case it is
the load operations that were deleted by InstCombine, please note that
once the load was removed there is no way to restore it back and that
prevents us from vectorizing the shuffle operation. There are probably
more similar issues where this approach could be applied.
I added phatom_mem(llvm_anyptr_ty, llvm_i64_ty) intrinsic for that,
indicating that for particular pointer let's call it %ptr we observed
maximum possible offset at which there was reference by its type in a
function. After InstCombine deleted the load operation, it could be
restored in SLPVectorizer and we could...
2017 Sep 13
2
RFC phantom memory intrinsic
...; the load operations that were deleted by InstCombine, please note that
> once the load was removed there is no way to restore it back and that
> prevents us from vectorizing the shuffle operation. There are probably
> more similar issues where this approach could be applied.
> I added phatom_mem(llvm_anyptr_ty, llvm_i64_ty) intrinsic for that,
> indicating that for particular pointer let's call it %ptr we observed
> maximum possible offset at which there was reference by its type in a
> function. After InstCombine deleted the load operation, it could be
> restored in SLPVec...
2017 Sep 13
2
RFC phantom memory intrinsic
...deleted by InstCombine, please note that
>>> once the load was removed there is no way to restore it back and that
>>> prevents us from vectorizing the shuffle operation. There are probably
>>> more similar issues where this approach could be applied.
>>> I added phatom_mem(llvm_anyptr_ty, llvm_i64_ty) intrinsic for that,
>>> indicating that for particular pointer let's call it %ptr we observed
>>> maximum possible offset at which there was reference by its type in a
>>> function. After InstCombine deleted the load operation, it could be...
2017 Sep 26
0
RFC phantom memory intrinsic
...ombine, please note that
>>>> once the load was removed there is no way to restore it back and that
>>>> prevents us from vectorizing the shuffle operation. There are probably
>>>> more similar issues where this approach could be applied.
>>>> I added phatom_mem(llvm_anyptr_ty, llvm_i64_ty) intrinsic for that,
>>>> indicating that for particular pointer let's call it %ptr we observed
>>>> maximum possible offset at which there was reference by its type in a
>>>> function. After InstCombine deleted the load operation,...
2017 Sep 26
2
RFC phantom memory intrinsic
...ote that
>>>>> once the load was removed there is no way to restore it back and that
>>>>> prevents us from vectorizing the shuffle operation. There are probably
>>>>> more similar issues where this approach could be applied.
>>>>> I added phatom_mem(llvm_anyptr_ty, llvm_i64_ty) intrinsic for that,
>>>>> indicating that for particular pointer let's call it %ptr we observed
>>>>> maximum possible offset at which there was reference by its type in a
>>>>> function. After InstCombine deleted the loa...
2017 Sep 26
0
RFC phantom memory intrinsic
...;>>>> once the load was removed there is no way to restore it back and that
>>>>>> prevents us from vectorizing the shuffle operation. There are probably
>>>>>> more similar issues where this approach could be applied.
>>>>>> I added phatom_mem(llvm_anyptr_ty, llvm_i64_ty) intrinsic for that,
>>>>>> indicating that for particular pointer let's call it %ptr we observed
>>>>>> maximum possible offset at which there was reference by its type in a
>>>>>> function. After InstCombine del...