Displaying 3 results from an estimated 3 matches for "c4f5e285".
2013 Jan 03
2
[LLVMdev] Does loop vectorizer inquire about target's SIMD capabilities?
On 3 January 2013 21:53, Nadav Rotem <nrotem at apple.com> wrote:
> > I am asking this because I would like to have loop vectorization
> disabled for targets that don't support SIMD instructions (for example,
> standard mips32).
> > Loop vectorization bloats the code size and prolongs compilation time
> without any improvement to performance for such targets.
>
2013 Jan 03
0
[LLVMdev] Does loop vectorizer inquire about target's SIMD capabilities?
On Jan 3, 2013, at 2:05 PM, Renato Golin <renato.golin at linaro.org> wrote:
> Isn't the vectorizer disabled by default?
The loop vectorizer is now enabled by default.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130103/4645b2e8/attachment.html>
2013 Jan 03
2
[LLVMdev] Does loop vectorizer inquire about target's SIMD capabilities?
...f -vectorization had to be passed explicitly to get it done on
production releases of LLVM or something else (-O4 or -OV, for example).
cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130103/c4f5e285/attachment.html>