This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Cost of inlining when the function has call to a target-specific builtin


On 9/16/07, Richard Guenther <richard.guenther@gmail.com> wrote:
> Possibly.  There are weights for size, time and for inlining (we should
> drop the latter in favor of using either size or time weights dependent
> on inlining goal).  So the target hook should take an extra parameter
> to select the mode used.  Though this requires re-organizing code too
> much for stage3.

I don't think there should be a difference in the context of the cost
in this case.  the target builtins will have the same cost if we are
dealing with inlining costs or duplicating costs.  It should be the
number of instructions it will expand to (or close to that).

-- Pinski


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]