Displaying 6 results from an estimated 6 matches for "getnonlocalpointerdepfrombb".
2013 Jan 16
1
[LLVMdev] llvm print-memdeps segfault
...cause display problems. If
you REALLY want to taste LLVM bitcode first-hand, you
can force output with the `-f' option.
0 opt 0x08eaf9a8
1 opt 0x08eaff24
2 0xb7753400 __kernel_sigreturn + 0
3 opt 0x08c00c19
llvm::MemoryDependenceAnalysis::getNonLocalPointerDepFromBB(llvm::PHITransAddr
const&, llvm::AliasAnalysis::Location const&, bool, llvm::BasicBlock*,
llvm::SmallVectorImpl<llvm::NonLocalDepResult>&,
llvm::DenseMap<llvm::BasicBlock*, llvm::Value*,
llvm::DenseMapInfo<llvm::BasicBlock*> >&, bool) + 3673
4 opt 0x08c0...
2016 Jul 20
2
load instruction erroneously removed by GVN v2
...m might be TBAA; invoking clang with
-fno-strict-aliasing makes the test pass (similarly, opt with -basicaa does
not make GVN transform the load). When I look at the C/C++ source code, 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...
2016 Jul 20
2
load instruction erroneously removed by GVN v2
...does
>> not make GVN transform the load). When I look at the C/C++ source code, I
>> cannot find any type-based aliasing violations from eyeballing.
>>
>
> Can you excerpt the 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
>>...
2016 Jul 20
2
load instruction erroneously removed by GVN v2
...he C/C++ source code, I
>>>> cannot find any type-based aliasing violations from eyeballing.
>>>>
>>>
>>> Can you excerpt the 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...
2015 Jul 21
6
[LLVMdev] GlobalsModRef (and thus LTO) is completely broken
...000000010e6cf0c0,
> QueryInst=0x000000010a1a20c8, Loc=0x00007fff5fbf6268, isLoad=true,
> BB=0x000000010a19ffa0, Cache=0x0000000100f9d568, NumSortedEntries=0) + 2165
> at MemoryDependenceAnalysis.cpp:965
> frame #5: 0x0000000103a0e3a9
> 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
> f...
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