From: Adrian Bunk <bunk@stusta.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] fs/adfs/adfs.h: "extern inline" doesn't make sense
Date: Mon, 22 Aug 2005 21:44:41 +0200 [thread overview]
Message-ID: <20050822194441.GF9927@stusta.de> (raw)
In-Reply-To: <43087A08.3080400@drzeus.cx>
On Sun, Aug 21, 2005 at 02:56:40PM +0200, Pierre Ossman wrote:
> Adrian Bunk wrote:
> > [ this time with a better subject ]
> >
> > "extern inline" doesn't make sense.
> >
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
>
> Isn't 'extern inline' an old gcc trick to force inlining? (instead of
> just hinting)
For gcc >= 3.1, we are already telling the compiler that it should
either inline the code or abort compilation.
"extern inline" doesn't make much sense. And it gives a warning with
-Wmissing-prototypes.
I'm currently cleaning up warnings with -Wmissing-prototypes to get them
to an acceptable level. -Wmissing-prototypes will help us to enforce a
coding style that will avoid a class of nasty runtime errors that are
currently sometimes hitting us.
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:[~2005-08-22 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 23:41 [2.6 patch] "extern inline" doesn't make sense Adrian Bunk
2005-08-19 23:44 ` [2.6 patch] fs/adfs/adfs.h: " Adrian Bunk
2005-08-20 16:20 ` Russell King
2005-08-21 12:56 ` Pierre Ossman
2005-08-22 19:44 ` 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=20050822194441.GF9927@stusta.de \
--to=bunk@stusta.de \
--cc=drzeus-list@drzeus.cx \
--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