Displaying 6 results from an estimated 6 matches for "getpointerdependencyfrom".
2009 Apr 13
1
[LLVMdev] MemoryDependenceAnalysis
On Apr 13, 2009, at 3:32 PM, Eli Friedman wrote:
> On Mon, Apr 13, 2009 at 9:06 AM, Anthony Danalis <adanalis at eecs.utk.edu
> > wrote:
>> How can I use MemoryDependenceAnalysis (or any other analysis for
>> that
>> matter) to gather that the instructions
>> j = N/2 (store i32 %11, i32* %j, align 4)
>> and
>> N = N+7 (store i32 %12, i32* %n,
2010 May 26
2
[LLVMdev] AliasAnalysis as a Loadable Module, Possible 2.6->2.7 issue
...FooAA::alias go to FooAA::print, resulting in
understandably painful failure thereafter, generally a segfault.
Example stack trace:
==25630== by 0xB2752F: llvm::Pass::print(llvm::raw_ostream&,
llvm::Module const*) const (Pass.cpp:94)
==25630== by 0x9B2769:
llvm::MemoryDependenceAnalysis::getPointerDependencyFrom(llvm::Value*,
unsigned long, bool, llvm::ilist_iterator<llvm::Instruction>,
llvm::BasicBlock*) (MemoryDependenceAnalysis.cpp:282)
And the related lines from MemDep:
282 if (AccessPtr == Inst ||
283 AA->alias(Inst, 1, AccessPtr, 1) == AliasAnalysis::MustAlias)
The way I mak...
2015 Aug 07
2
load instruction erroneously removed by GVN
...here is also
call fastcc void @format_long(i16* %_tmp30, i16 10, i32 10), !dbg !22
which will use %_tmp30 to write in the alloca'd buffer.
Shoulnd't MemoryDependenceAnalysis::getDependency rather return the call?
MemoryDependenceAnalysis::getDependency uses
MemoryDependenceAnalysis::getPointerDependencyFrom, which does the
following analysis at the end:
// See if this instruction (e.g. a call or vaarg) mod/ref's the
pointer.
AliasAnalysis::ModRefResult MR = AA->getModRefInfo(Inst, MemLoc);
// If necessary, perform additional analysis.
if (MR == AliasAnalysis::ModRef)...
2013 Jan 21
2
[LLVMdev] llvm alloca dependencies
...he results were not correct. For instance,
`MemoryDependenceAnalysis::getDependency` should be good with option "Def",
but works only for stores, not for loads. Also I have a segfault when
trying to use `MemoryDependenceAnalysis::getNonLocalPointerDependency` or
`MemoryDependenceAnalysis::getPointerDependencyFrom` . When I try to check
my result using MemDepResult::getDef(), the result for Load instructions is
the same instruction ! So its depending on itself, that being weird since
it is using a variable that is previously defined in the code.
I also was no able to use DependenceAnalysis::depends() or get...
2015 Jul 21
6
[LLVMdev] GlobalsModRef (and thus LTO) is completely broken
...odRef.cpp:562
> frame #2: 0x00000001038d6aa8
> libLTO.dylib`llvm::AliasAnalysis::getModRefInfo(this=0x000000010eba5c30,
> S=0x000000010a1a22e0, Loc=0x00007fff5fbf6268) + 120 at AliasAnalysis.cpp:288
> frame #3: 0x0000000103a0a814
> libLTO.dylib`llvm::MemoryDependenceAnalysis::getPointerDependencyFrom(this=0x000000010e6cf0c0,
> MemLoc=0x00007fff5fbf6268, isLoad=true, ScanIt=llvm::BasicBlock::iterator at
> 0x00007fff5fbf4390, BB=0x000000010a19ffa0, QueryInst=0x000000010a1a20c8) +
> 1908 at MemoryDependenceAnalysis.cpp:570
> frame #4: 0x0000000103a0ffa5
> libLTO.dylib`llvm::Memo...
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