public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [patch 01/2] allow gcc4 to control inlining
Date: Wed, 28 Dec 2005 08:36:10 -0600	[thread overview]
Message-ID: <20051228143610.GK3356@waste.org> (raw)
In-Reply-To: <20051228143442.GA14986@elte.hu>

On Wed, Dec 28, 2005 at 03:34:42PM +0100, Ingo Molnar wrote:
> 
> * Matt Mackall <mpm@selenic.com> wrote:
> 
> > On Wed, Dec 28, 2005 at 12:46:53PM +0100, Ingo Molnar wrote:
> > > allow gcc4 compilers to decide what to inline and what not - instead
> > > of the kernel forcing gcc to inline all the time.
> > > 
> > > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> > > Signed-off-by: Arjan van de Ven <arjan@infradead.org>
> > 
> > I'm ever so slightly wary of GCC 4's stack size logic for functions 
> > with nested scopes, but I think we'll have no trouble catching any 
> > trouble cases in 2.6.16-rc.
> > 
> > Acked-by: Matt Mackall <mpm@selenic.com>
> 
> FYI, the max function-frame size did not change, so there's no 
> outrageous frames like with gcc3, just a small shift upwards.

My point is more that I wouldn't be surprised if we found a corner
case for a particular .config. But even with GCC 3 and 4k stacks,
automatic inlining worked just fine for most configs after killing
just a few offenders.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2005-12-28 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28 11:46 [patch 01/2] allow gcc4 to control inlining Ingo Molnar
2005-12-28 14:26 ` Matt Mackall
2005-12-28 14:34   ` Ingo Molnar
2005-12-28 14:36     ` Matt Mackall [this message]
2005-12-28 14:39 ` Roland Dreier
2005-12-28 14:53   ` Ingo Molnar
2005-12-28 18:39 ` Al Viro
2005-12-28 19:51   ` Arjan van de Ven

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=20051228143610.GK3356@waste.org \
    --to=mpm@selenic.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@osdl.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