On Fri, Oct 03, 2014 at 12:36:37PM -0600, Jeff Law wrote: > rtx_cost and its friends have always been a problem and it's always felt > like a design problem. The true cost of something is so context > dependent I'm not really sure how to build an API to do this in a sane way.
In many places it already would help if we had an rtx_insn_cost that gets a full insn as input. Maybe an rtx_set_src_cost for the other cases where "cost of an RTX" makes any sense at all. Segher
