[llvm-commits] Cost Table, take 3

Chandler Carruth chandlerc at google.com
Thu Jan 24 13:06:08 PST 2013


This code (and your plan) makes perfect sense to me.

I would suggest putting it in its own header, or in some other header under
include/llvm/Target --- the consumers of the analysis aren't the ones that
want it.


On Thu, Jan 24, 2013 at 12:42 PM, Renato Golin <renato.golin at linaro.org>wrote:

> Hi folks,
>
> Now it's simple and stupid. ;)
>
> I just moved the functions up and made them templates on the type to avoid
> the inclusion of foreign headers. I think this was Chandler's
> recommendation all along, and I got lost in the number of changes.
>
> For now, since they're only two tables, I'd rather keep them as they are
> and see if the pattern grows. If it doesn't, leave it. If it does, we think
> of a better solution overall.
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130124/3299faf7/attachment.html>


More information about the llvm-commits mailing list