This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] costs and it's use in assign_reg_parm
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Jeff Law <law at redhat dot com>
- Cc: Ramana Radhakrishnan <ramana dot radhakrishnan at arm dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 3 Oct 2014 21:54:30 -0500
- Subject: Re: [RFC] costs and it's use in assign_reg_parm
- Authentication-results: sourceware.org; auth=none
- References: <542D0D4D dot 3000709 at arm dot com> <542EECB5 dot 4070904 at redhat dot com>
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