This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: INTEGRATE_THRESHOLD ever changed?
- To: Joe Buck <jbuck at possibly dot synopsys dot com>
- Subject: Re: INTEGRATE_THRESHOLD ever changed?
- From: Stan Shebs <shebs at apple dot com>
- Date: Fri, 17 Mar 2000 12:33:37 -0800
- Cc: gcc at gcc dot gnu dot org
- Organization: Core Tools, Apple Computer
- References: <200003171738.JAA10302@possibly.synopsys.com>
- Reply-To: shebs at apple dot com
Joe Buck wrote:
> > The macro INTEGRATE_THRESHOLD is defined and documented as a possibly
> > target-specific heuristic to help decide when to inline functions.
> > However, I don't see that any target actually uses anything but the
> > default formula, which is 8 * (8 + num_arguments) instructions.
>
> Actually, a different formula is used if -Os is supplied, giving a smaller
> threshold (inlining can still make sense when optimizing for space where
> the function is very small, something that is common for C++ member
> functions), but I guess you know about that one. (see the definition in
> integrate.c).
Yeah, I was simplifying the background a bit.
> I see a comment saying "This is overridden on RISC machines" -- if that's
> a lie, the comment should be changed.
Grepping through all the sources and subdirs didn't show me *anything*
that changed it, so if it's being overridden on RISC machines, it must
done in some way that's too subtle for me to see it - wouldn't be the
first time that's happened though! :-)
Stan