public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1
Date: Thu, 26 Jul 2001 17:57:35 -0700	[thread overview]
Message-ID: <20010726175735.A20320@twiddle.net> (raw)
In-Reply-To: <9C117960438@vcnet.vc.cvut.cz>
In-Reply-To: <9C117960438@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Thu, Jul 26, 2001 at 08:28:32PM +0000

On Thu, Jul 26, 2001 at 08:28:32PM +0000, Petr Vandrovec wrote:
> Just adding '-finline-limit=150' fixes all of them (critical limit
> is somewhere between 120 and 150 on my kernel). As '-finline-limit'
> is documented as being 10000 by default, it looks like that someone
> changed default value to some really unreasonable value (probably 100).

Yes.  The higher value resulted in much compile-time lossage on
heavily templated c++ code, as it proceeded to inline everything
in sight.

While we may not use 100 in the final 3.0.1, it will definitely
be much lower than 10000.  More intelligent heuristics will have
to wait for 3.1 or something.


r~

  reply	other threads:[~2001-07-27  1:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 20:28 [PATCH] gcc-3.0.1 and 2.4.7-ac1 Petr Vandrovec
2001-07-27  0:57 ` Richard Henderson [this message]
2001-07-27  3:12   ` Linus Torvalds
2001-07-27  6:44     ` Wayne Whitney
2001-07-27 16:03 ` Florian Weimer
  -- strict thread matches above, loose matches on Subject: below --
2001-07-27 18:14 Petr Vandrovec
2001-07-26 17:48 Petr Vandrovec
2001-07-26 17:52 ` Alan Cox
2001-07-26 20:12   ` Linus Torvalds
2001-07-27  6:55     ` Niels Kristian Bech Jensen
2001-07-27  8:34       ` Robert Schiele
2001-07-26 17:55 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010726175735.A20320@twiddle.net \
    --to=rth@twiddle.net \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox