From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org, Terrence.Miller@sun.com
Cc: Jakub Jelinek <jakub@redhat.com>, Adrian Bunk <bunk@stusta.de>,
Michael Matz <matz@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [discuss] [2.6 patch] include/asm-x86_64 "extern inline" -> "static inline"
Date: Tue, 6 Sep 2005 22:23:50 +0200 [thread overview]
Message-ID: <200509062223.50747.ak@suse.de> (raw)
In-Reply-To: <431DD7BE.7060504@Sun.COM>
I don't think the functionality of having single copies in case
an out of line version was needed was ever required by the Linux kernel.
extern inline was used in the kernel a long time ago as a "poor man's
-Winline". Basically the intention was to get an linker error
if the inlining didn't work for some reason because if we say
inline we mean inline.
But that's long obsolete because the requirements of the C++ "template is
turing complete" people has broken inlining so badly (they want a lot of
inlining, but not too much inlining because otherwise their compile times
explode and the heuristics needed for making some of these pathologic cases
work seems to break a lot of other sane code) that the kernel was forced to
define inline to __attribute__((always_inline)). And with that you get an
error if inlining
fails.
So the original purpose if extern inline is fulfilled by static inline now.
However extern inline also doesn't hurt, it really makes no difference now.
-Andi
next prev parent reply other threads:[~2005-09-06 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 20:31 [2.6 patch] include/asm-x86_64 "extern inline" -> "static inline" Adrian Bunk
2005-09-05 8:52 ` [discuss] " Michael Matz
2005-09-05 18:00 ` Adrian Bunk
2005-09-05 18:47 ` Jakub Jelinek
2005-09-05 19:00 ` Adrian Bunk
2005-09-06 4:38 ` H. Peter Anvin
2005-09-06 17:54 ` Terrence Miller
2005-09-06 20:23 ` Andi Kleen [this message]
2005-09-06 20:32 ` David S. Miller
2005-09-06 20:55 ` Terrence Miller
2005-09-06 21:41 ` Michael Matz
2005-09-07 0:07 ` H. Peter Anvin
2005-09-06 21:49 ` Andi Kleen
2005-09-05 23:25 ` Andi Kleen
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=200509062223.50747.ak@suse.de \
--to=ak@suse.de \
--cc=Terrence.Miller@sun.com \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
/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