[llvm-commits] [llvm] r167324 - in /llvm/trunk: include/llvm/Analysis/Passes.h include/llvm/InitializePasses.h include/llvm/LinkAllPasses.h lib/Analysis/Analysis.cpp lib/Analysis/CMakeLists.txt lib/Analysis/CostModel.cpp test/Analysis/CostModel/ te...

[Nadav Rotem]

On Nov 5, 2012, at 5:10 AM, David Tweed <david.tweed at arm.com> wrote:

> ReHi,
> 
> About the only comment I've got is that, while this is clearly an initial
> stub, supposing one were to obtain independent information about the
> vectorisation cost from somewhere for various CPUs, would there be enough
> freedom to move the internals to accommodate a huge set of tables detailing
> costs per CPU?

Definitely.  We still need to discuss the best way to represent this.  For example, should we use tablegen to generate the tables ?  

> It looks like there's freedom to plug in any other
> implementation behind the interface, but it's probably as well to check.

Every target can have a different implementation. 

> (I
> also note that this is based up on the cost for a single instruction, which
> is probably the way to go for simplicity, at least for the initial
> implementation.) 
> 
> Regards,
> Dave
> 

Thanks,
Nadav