mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: schwidefsky@de.ibm.com
Cc: bunk@stusta.de, linux390@de.ibm.com, linux-390@vm.marist.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] arch/s390/Makefile: remove -finline-limit=10000
Date: Wed, 11 Jan 2006 11:56:29 -0800 (PST)	[thread overview]
Message-ID: <20060111.115629.65083150.davem@davemloft.net> (raw)
In-Reply-To: <1136971280.6147.20.camel@localhost.localdomain>

From: Martin Schwidefsky <schwidefsky@de.ibm.com>
Date: Wed, 11 Jan 2006 10:21:20 +0100

> On Tue, 2006-01-10 at 21:57 +0100, Adrian Bunk wrote:
> > -finline-limit might have been required for older compilers, but 
> > nowadays it does no longer make sense.
> 
> I didn't check the effects of reverting to the default inline-limit, did
> you find any negative impacts? I'm thinking about the critical code
> paths e.g. minor faults. There better should not be an additional
> function call that would have been inlined with the bigger inline limit,
> since function calls are quite expensive on s390.

You need to be careful now that -Os is specified by default
in 2.6.x

The inline-limit GCC option is interpreted differently in
gcc-4.x when -Os is given vs. when it is not.

On Sparc this caused schedule() to be inlined (I'm not kidding)
which caused all kinds of troubles.

I highly recommed you don't specify it and let the compiler
make the decisions, and add inline tags to places where you
think it is hyper-important for inlining to occur.

  reply	other threads:[~2006-01-11 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 20:57 Adrian Bunk
2006-01-11  9:21 ` Martin Schwidefsky
2006-01-11 19:56   ` David S. Miller [this message]
2006-02-03 21:15 Adrian Bunk

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=20060111.115629.65083150.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bunk@stusta.de \
    --cc=linux-390@vm.marist.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux390@de.ibm.com \
    --cc=schwidefsky@de.ibm.com \
    /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

all inboxes | Powered by JetHome®