From: Adrian Bunk <bunk@stusta.de>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Andrew Morton <akpm@osdl.org>,
matthew@wil.cx, kyle@parisc-linux.org,
parisc-linux@parisc-linux.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] parisc: "extern inline" -> "static inline" (fwd)
Date: Fri, 1 Dec 2006 17:54:27 +0100 [thread overview]
Message-ID: <20061201165427.GD11084@stusta.de> (raw)
In-Reply-To: <20061201164354.GA10549@colo.lackof.org>
On Fri, Dec 01, 2006 at 09:43:54AM -0700, Grant Grundler wrote:
> On Fri, Dec 01, 2006 at 12:48:11PM +0100, Adrian Bunk wrote:
> > "extern inline" generates a warning with -Wmissing-prototypes and I'm
> > currently working on getting the kernel cleaned up for adding this to
> > the CFLAGS since it will help us to avoid a nasty class of runtime
> > errors.
>
>
> John David Anglin is the hppa/parisc gcc maintainer and has
> commented on inline variants last year:
> http://lists.parisc-linux.org/pipermail/parisc-linux/2005-October/027587.html
>
> This makes me think -Wmissing-prototypes is reporting the wrong warning.
> ie there is a prototype but no function and no label.
> Can you check with gcc folks to see if this is a gcc bug?
>
> The parisc point intentionally switched to "extern inline" at one
> point and unless what jda wrote is now incorrect, I'm not inclined
> to change it.
If you read John David Anglin's email, you'll note that if you take the
address you need this function provided somewhere.
Which of the functions my patch changes also have a global function
provided within the kernel?
If none, "extern inline" didn't make any sense.
> > If there are places that really need a forced inline, __always_inline
> > would be the correct solution.
>
> Yes, all the functions marked "extern inline" are expected to get
> essentially the same treatment as "always_inline".
Currently, "inline" is defined to be always_inline, and
__always_inline is for cases that produce non-compiling or non-working
(opposed to only suboptimal) code.
> thanks,
> grant
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
next prev parent reply other threads:[~2006-12-01 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 11:48 [2.6 patch] parisc: "extern inline" -> "static inline" (fwd) Adrian Bunk
2006-12-01 16:43 ` [parisc-linux] " Grant Grundler
2006-12-01 16:43 ` Grant Grundler
2006-12-01 16:54 ` Adrian Bunk [this message]
2006-12-01 17:36 ` Grant Grundler
2006-12-01 17:36 ` [parisc-linux] " Grant Grundler
2006-12-01 16:54 ` Adrian Bunk
2006-12-01 17:38 ` [parisc-linux] Re: [2.6 patch] parisc: "extern inline" -> "static John David Anglin
2006-12-01 17:38 ` John David Anglin
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=20061201165427.GD11084@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.