public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: grundler@parisc-linux.org, linux-kernel@vger.kernel.org,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static inline"
Date: Sun, 30 Oct 2005 16:56:24 +0100	[thread overview]
Message-ID: <20051030155624.GG4180@stusta.de> (raw)
In-Reply-To: <20051030152215.GB9235@parisc-linux.org>

On Sun, Oct 30, 2005 at 08:22:15AM -0700, Matthew Wilcox wrote:
> On Sun, Oct 30, 2005 at 02:03:01AM +0200, Adrian Bunk wrote:
> > "extern inline" doesn't make much sense.
> 
> Are you sure?  It used to.  Taking just one sample, pgd_none:
> 
> extern inline: alpha, parisc, s390
> static inline: frv, ppc, sh64
> define: arm, arm26, frv, h8300, m68knommu, ppc64, v850
> 
> I really don't think it makes any difference.  Such a function (returning
> always 0) is always going to be inlined, and the only difference between
> static inline and extern inline is what happens when it can't be inlined.

On !alpha we are defining inline to __attribute__((always_inline)) for 
any non-ancient gcc making this a zero difference.

The bigger issue is that "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.

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


  reply	other threads:[~2005-10-30 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30  0:03 [2.6 patch] parisc: "extern inline" -> "static inline" Adrian Bunk
2005-10-30 15:22 ` [parisc-linux] " Matthew Wilcox
2005-10-30 15:56   ` Adrian Bunk [this message]
2005-10-30 16:42     ` [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static John David Anglin
2005-10-30 17:14       ` Adrian Bunk
2005-11-02 13:48   ` [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static inline" Jan Engelhardt
2005-11-02 13:53     ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2006-08-19 17:19 Adrian Bunk
2006-08-21 14:42 ` [parisc-linux] " Kyle McMartin

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=20051030155624.GG4180@stusta.de \
    --to=bunk@stusta.de \
    --cc=grundler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox