From: Adrian Bunk <bunk@fs.tum.de>
To: Jan Hubicka <jh@suse.cz>
Cc: Andi Kleen <ak@muc.de>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add -Winline
Date: Sat, 17 Jan 2004 02:12:47 +0100 [thread overview]
Message-ID: <20040117011246.GC12027@fs.tum.de> (raw)
In-Reply-To: <20040115125544.GL5018@kam.mff.cuni.cz>
On Thu, Jan 15, 2004 at 01:55:44PM +0100, Jan Hubicka wrote:
> > On Wed, Jan 14, 2004 at 10:07:43AM +0100, Andi Kleen wrote:
> > >
> > > Add -Winline by default. This makes the compiler warn when something
> > > marked inline is not getting inlined. This is often because the
> > >
> > > It should only make a difference with gcc 3.4, because in earlier
> > > compilers we use always_inline and not inlining with always_inline
> > > is an error already.
> > >...
> >
> > Attached are all inlining warnings I get with this patch applied in
> > 2.6.1-mm3 using gcc 3.3.3 20040110 (prerelease) (Debian).
> >
> > I've gzip'ed it since it was > 100 kB.
> >
> > A few warnings might be missing since I used a .config with
> > CONFIG_SMP=y.
>
> Are you sure that you do use always_inline? (ie can you look into one
> of preprocessed file for declaration of some of failed functions?)
Yes, e.g. in drivers/ieee1394/eth1394.c:
<-- snip -->
...
static __inline__ __attribute__((always_inline)) __attribute__((always_inline))
void purge_partial_datagram(struct list_head *old)
{
...
<-- snip -->
> Honza
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2004-01-17 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 9:07 [PATCH] Add -Winline Andi Kleen
2004-01-15 12:42 ` Adrian Bunk
2004-01-15 12:55 ` Jan Hubicka
2004-01-17 1:12 ` Adrian Bunk [this message]
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=20040117011246.GC12027@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jh@suse.cz \
--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