search for: canvecmem

Displaying 4 results from an estimated 4 matches for "canvecmem".

2015 Mar 19
2
[LLVMdev] RFC: Loop versioning for LICM
...)) { > 1030 emitAnalysis( > 1031 LoopAccessReport(ST) > 1032 << "write to a loop invariant address could not be vectorized"); > 1033 DEBUG(dbgs() << "LAA: We don't allow storing to uniform addresses\n"); > 1034 CanVecMem = false; > 1035 return; > 1036 } > > LAA is ignoring the cases where store is loop invariant, it sets memory can’t be vectorize. > > In loop versioning for LICM, we are more interested in loop invariant cases. > Invariant store is one of the important case for “LIC...
2015 Mar 20
2
[LLVMdev] RFC: Loop versioning for LICM
...)) { > 1030 emitAnalysis( > 1031 LoopAccessReport(ST) > 1032 << "write to a loop invariant address could not be vectorized"); > 1033 DEBUG(dbgs() << "LAA: We don't allow storing to uniform addresses\n"); > 1034 CanVecMem = false; > 1035 return; > 1036 } > > LAA is ignoring the cases where store is loop invariant, it sets memory can’t be vectorize. > > In loop versioning for LICM, we are more interested in loop invariant cases. > Invariant store is one of the important case for “LI...
2015 Mar 24
3
[LLVMdev] RFC: Loop versioning for LICM
...)) { > 1030 emitAnalysis( > 1031 LoopAccessReport(ST) > 1032 << "write to a loop invariant address could not be vectorized"); > 1033 DEBUG(dbgs() << "LAA: We don't allow storing to uniform addresses\n"); > 1034 CanVecMem = false; > 1035 return; > 1036 } > > LAA is ignoring the cases where store is loop invariant, it sets memory can’t be vectorize. > > In loop versioning for LICM, we are more interested in loop invariant cases. > Invariant store is one of the important case for “LI...
2015 Mar 11
2
[LLVMdev] RFC: Loop versioning for LICM
> On Mar 5, 2015, at 10:33 PM, Nema, Ashutosh <Ashutosh.Nema at amd.com> wrote: > > > I am about to post the patches to make LAA suitable for Loop Distribution. As you will hopefully find this will make the LAA more generic. I will cc you on the patches. > > Sure Adam. > > RuntimeCheckEmitter > “RuntimeCheckEmitter::addRuntimeCheck” > While creating