search for: vectorizationpass

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

2009 Dec 17
2
[LLVMdev] Automatic Vectorization
...IR. Would that spoil any other pass? What passes should run before/after such a pass? I believe that would be a FunctionPass and registered in the LoopDependencyAnalysis "runOnLoop()", so it can run when such pass is called by the PassManager. Or should it be a completely separate pass (VectorizationPass?) so we can control it from a separate command-line flag? Any comments appreciated before I dig in. cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm
2010 Jan 04
0
[LLVMdev] Automatic Vectorization
...09 AM, Renato Golin <rengolin at systemcall.org> wrote: > > I believe that would be a FunctionPass and registered in the > LoopDependencyAnalysis "runOnLoop()", so it can run when such pass is > called by the PassManager. Or should it be a completely separate pass > (VectorizationPass?) so we can control it from a separate command-line > flag? > A separate VectorizationPass that requires dependence analysis is the way to go. - Devang
2009 Dec 16
0
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
Hello, Erwin > Although most of this is plain portable C++ perhaps LLVM can auto-vectorize > some of this? Well, I doubt so, unfortunately - LLVM does not have any autopar these days > There is a little bit of hand optimized x86 SSE code. This is only enabled > on 32bit Windows and Mac OSX Intel builds. Ok. What's about Linux builds? Are there any other implementations e.g.
2009 Dec 16
6
[LLVMdev] Help adding the Bullet physics sdk benchmark to the LLVM test suite?
Hi Anton, Thanks a lot for offering help. Bullet uses basic linear algebra with 4-way vectors, quaternion and matrices. Although most of this is plain portable C++ perhaps LLVM can auto-vectorize some of this? There is a little bit of hand optimized x86 SSE code. This is only enabled on 32bit Windows and Mac OSX Intel builds. >> Should I just use the 2.75 release? If you are interested,