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

From: "Pranav Bhandarkar" <pranav dot bhandarkar at gmail dot com>
To: "Richard Guenther" <richard dot guenther at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Mon, 17 Sep 2007 00:46:39 +0530
Subject: Re: [PATCH] Cost of inlining when the function has call to a target-specific builtin
References: <649555d50709160703x593bf9f3o5635ecb3fe8d38b9@mail.gmail.com> <84fc9c000709161159m57aaf3c7hf3fc9388485b1815@mail.gmail.com>

> This doesn't fit with the modularized cost metrics we have.  That is,
> estimate_num_insns_1 is not only used for inlining.

The comments for estimate_num_insns_1 say
/* Used by estimate_num_insns.  Estimate number of instructions seen
   by given statement.  */

>From this my understanding is that even If esimate_num_insns_1 is not
used only for inlining, wouldnt it be better to get, from the backend,
 a more accurate count of the number of instructions seen by a call to
a target_specific builtin ?

If estimate_num_insns_1 isnt used only for inlining maybe the name of
the hook should change ?

cheers!
Pranav

Follow-Ups:
- Re: [PATCH] Cost of inlining when the function has call to a target-specific builtin
  - From: Richard Guenther

References:
- [PATCH] Cost of inlining when the function has call to a target-specific builtin
  - From: Pranav Bhandarkar
- Re: [PATCH] Cost of inlining when the function has call to a target-specific builtin
  - From: Richard Guenther

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