Displaying 5 results from an estimated 5 matches for "skipfirstblock".
2016 Jul 20
2
load instruction erroneously removed by GVN v2
...e, I
cannot find any type-based aliasing violations from eyeballing.
I started looking at the aliasing and landed at
getNonLocalPointerDepFromBB(), in which the worklist algorithm to find
MemDep reported the result from the init block, ignoring all the kills
after it. I did see one of the parm was SkipFirstBlock and this appears to
ignore the store %ptr above the load. Is there a reason why it skips first
block? Shouldn't it look at the preceding instructions in the same block as
they could contain kill points? I am still unfamiliar with the algorithm
used here and would very much appreciate if someone...
2016 Jul 20
2
load instruction erroneously removed by GVN v2
...actual source code?
>
>>
>> I started looking at the aliasing and landed at
>> getNonLocalPointerDepFromBB(), in which the worklist algorithm to find
>> MemDep reported the result from the init block, ignoring all the kills
>> after it. I did see one of the parm was SkipFirstBlock and this appears to
>> ignore the store %ptr above the load. Is there a reason why it skips first
>> block?
>>
>
>
> Yes. It is looking for *non-local* dependences. The block it should skip
> is bb2, not loop1.
> There is another call for local dependences. If you...
2016 Jul 20
2
load instruction erroneously removed by GVN v2
...;
>>>> I started looking at the aliasing and landed at
>>>> getNonLocalPointerDepFromBB(), in which the worklist algorithm to find
>>>> MemDep reported the result from the init block, ignoring all the kills
>>>> after it. I did see one of the parm was SkipFirstBlock and this appears to
>>>> ignore the store %ptr above the load. Is there a reason why it skips first
>>>> block?
>>>>
>>>
>>>
>>> Yes. It is looking for *non-local* dependences. The block it should
>>> skip is bb2, not loop1.
&...
2015 Jul 21
6
[LLVMdev] GlobalsModRef (and thus LTO) is completely broken
...3a9
> libLTO.dylib`llvm::MemoryDependenceAnalysis::getNonLocalPointerDepFromBB(this=0x000000010e6cf0c0,
> QueryInst=0x000000010a1a20c8, Pointer=0x00007fff5fbf62a8,
> Loc=0x00007fff5fbf6268, isLoad=true, StartBB=0x000000010a19ffa0,
> Result=0x00007fff5fbf6bf0, Visited=0x00007fff5fbf6208, SkipFirstBlock=false)
> + 5897 at MemoryDependenceAnalysis.cpp:1200
> frame #6: 0x0000000103a0cb3b
> libLTO.dylib`llvm::MemoryDependenceAnalysis::getNonLocalPointerDependency(this=0x000000010e6cf0c0,
> QueryInst=0x000000010a1a20c8, Result=0x00007fff5fbf6bf0) + 635 at
> MemoryDependenceAnalysis....
2015 Jul 17
2
[LLVMdev] GlobalsModRef (and thus LTO) is completely broken
On Fri, Jul 17, 2015 at 9:13 AM Evgeny Astigeevich <
evgeny.astigeevich at arm.com> wrote:
> It’s Dhrystone.
>
Dhrystone has historically not been a good indicator of real-world
performance fluctuations, especially at this small of a shift.
I'd like to see if we see any fluctuation on larger and more realistic
application benchmarks. One advantage of the flag being set is that we