From: Adrian Bunk <bunk@stusta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Alpha: replacing "extern inline"
Date: Thu, 24 Aug 2006 00:53:03 +0200 [thread overview]
Message-ID: <20060823225303.GD19810@stusta.de> (raw)
In-Reply-To: <20060821215526.GA22930@twiddle.net>
On Mon, Aug 21, 2006 at 02:55:26PM -0700, Richard Henderson wrote:
> On Mon, Aug 21, 2006 at 01:54:38AM +0200, Adrian Bunk wrote:
> > Why?
>
> Because it inlines when it needs to, and does not generate
> out of line code when its address is taken.
Ah, I start to remember.
Is this actually used anywhere in the kernel?
> > Can someone tell me which of the Alpha "static inline"'s need for some
> > reason an __always_inline?
>
> There shouldn't be any.
>
> > Does the never defined __IO_EXTERN_INLINE still have any purpose?
>
> It is defined.
>
> $ grep 'define __IO_EXTERN_INLINE' * | wc -l
> 12
Ups, I was blind...
> r~
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:[~2006-08-23 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 23:54 Alpha: replacing "extern inline" Adrian Bunk
2006-08-21 21:55 ` Richard Henderson
2006-08-23 22:53 ` 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=20060823225303.GD19810@stusta.de \
--to=bunk@stusta.de \
--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