Displaying 3 results from an estimated 3 matches for "47e4376b".
2013 Jun 24
1
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
...nd strategy) to vectorize is based on a cost model, so the later
we do it the more information we can use in the cost model to make the
correct decision.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130624/47e4376b/attachment.html>
2013 Jun 24
0
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
----- Original Message -----
> Hi,
>
> I wanted to start a discussion about the following issue since I am
> not sure about what to do about it:
>
> The loop-vectorizer has the potential to make code a quite a bit
> bigger (esp. in cases where we don’t know the loop count or whether
> pointers alias).
> Chandler has observed this in snappy where we have a simple
2013 Jun 24
8
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
Hi,
I wanted to start a discussion about the following issue since I am not sure about what to do about it:
The loop-vectorizer has the potential to make code a quite a bit bigger (esp. in cases where we don’t know the loop count or whether pointers alias).
Chandler has observed this in snappy where we have a simple memory copying loop (that may overlap).
We vectorize this loop and then this