Displaying 6 results from an estimated 6 matches for "184698".
Did you mean:
14698
2013 Jun 24
8
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
...ignificant(?) degradation.
https://code.google.com/p/snappy/source/browse/trunk/snappy.cc#99
We have seen some good performance benefits from vectorizing such loops. So not vectorizing them is not really a good option I think.
In <http://llvm.org/viewvc/llvm-project?view=revision&revision=184698> Chandler introduced a flag so that we can run the vectorizer after all CG passes. This would prevent the inline from seeing the vectorized code.
I see some potential issues:
* We run a loop pass later again with the associated compile time cost (?)
* The vectorizer relies on cleanup passes t...
2013 Jun 24
1
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
On Mon, Jun 24, 2013 at 12:32 PM, Hal Finkel <hfinkel at anl.gov> wrote:
> > In
> > <http://llvm.org/viewvc/llvm-project?view=revision&revision=184698>
> > Chandler introduced a flag so that we can run the vectorizer after
> > all CG passes. This would prevent the inline from seeing the
> > vectorized code.
>
> There are obviously several issues here, and they seem only loosely
> related. Regarding this first one, wh...
2013 Jun 24
0
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
...tps://code.google.com/p/snappy/source/browse/trunk/snappy.cc#99
>
> We have seen some good performance benefits from vectorizing such
> loops. So not vectorizing them is not really a good option I think.
>
> In
> <http://llvm.org/viewvc/llvm-project?view=revision&revision=184698>
> Chandler introduced a flag so that we can run the vectorizer after
> all CG passes. This would prevent the inline from seeing the
> vectorized code.
There are obviously several issues here, and they seem only loosely related. Regarding this first one, why is the right answer not to...
2013 Jun 24
0
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
...;
> https://code.google.com/p/snappy/source/browse/trunk/snappy.cc#99
>
> We have seen some good performance benefits from vectorizing such loops. So not vectorizing them is not really a good option I think.
>
> In <http://llvm.org/viewvc/llvm-project?view=revision&revision=184698> Chandler introduced a flag so that we can run the vectorizer after all CG passes. This would prevent the inline from seeing the vectorized code.
>
> I see some potential issues:
>
> * We run a loop pass later again with the associated compile time cost (?)
I want to move loop opt...
2013 Jun 24
0
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
On Mon, Jun 24, 2013 at 11:01 AM, Arnold Schwaighofer <
aschwaighofer at apple.com> wrote:
> In <http://llvm.org/viewvc/llvm-project?view=revision&revision=184698>
> Chandler introduced a flag so that we can run the vectorizer after all CG
> passes. This would prevent the inline from seeing the vectorized code.
>
Just for the record, I have no real expectation that this is a good idea
yet... But it's hard to collect numbers without a flag of...
2013 Jun 24
2
[LLVMdev] [llvm] r184698 - Add a flag to defer vectorization into a phase after the inliner and its
...ps://code.google.com/p/snappy/source/browse/trunk/snappy.cc#99
>
> We have seen some good performance benefits from vectorizing such
> loops. So not vectorizing them is not really a good option I think.
>
> In <
> http://llvm.org/viewvc/llvm-project?view=revision&revision=184698 >
> Chandler introduced a flag so that we can run the vectorizer after
> all CG passes. This would prevent the inline from seeing the
> vectorized code.
>
> I see some potential issues:
>
> * We run a loop pass later again with the associated compile time
> cost (?)
>...