This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ compile-time regressions
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: C++ compile-time regressions
- From: aoliva at redhat dot com
- Date: 02 Aug 2001 16:25:22 -0300
- Cc: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, Joe Buck <jbuck at synopsys dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Organization: GCC Team, Red Hat
- References: <16520000.996778655@warlock.codesourcery.com>
On Aug 2, 2001, Mark Mitchell <mark@codesourcery.com> wrote:
>> But I wonder if the default value of PARAM_MAX_INLINE_INSNS should be
>> a property of the target machine. Different targets have different
>> INSN densities. I don't know how much this changes from one target to
>> another in the early rtl stages used for rtl inlining, though... Does
>> anyone more experienced think it would be worth the trouble? I could
>> produce a patch to make the default target-modifiable.
> I think we're tackling this from the wrong angle.
I think I wasn't clear. My suggestion didn't mean to affect compile
time, but rather, to offer a reasonably similar behavior across
multiple targets, in regards to inlining or not inlining functions.
Using the same threshold on targets with very different INSN densities
is deemed to get fewer functions inlined on targets with smaller INSN
densities. I suppose it would be desirable to inline pretty much the
same functions, regardless of the target.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me