From: Adrian Bunk <bunk@fs.tum.de>
To: Andi Kleen <ak@muc.de>
Cc: Tim Bird <tim.bird@am.sony.com>, linux-kernel@vger.kernel.org
Subject: Re: Is extern inline -> static inline OK?
Date: Sat, 7 Aug 2004 03:26:15 +0200 [thread overview]
Message-ID: <20040807012614.GC17708@fs.tum.de> (raw)
In-Reply-To: <m3657vj1bn.fsf@averell.firstfloor.org>
On Sat, Aug 07, 2004 at 01:26:04AM +0200, Andi Kleen wrote:
> Tim Bird <tim.bird@am.sony.com> writes:
> >
> > From what I have read, for either 'extern inline' or 'static inline'
> > the compiler is free to not inline the code. Is this wrong?
>
> Yes, it's wrong in current Linux 2.6. It currently defines inline to
> inline __attribute__((always_inline))
>...
To be more exact:
It's defined this way in both 2.4 and 2.6, but only for gcc >= 3.1
(which support __attribute__((always_inline)) ).
> Hope this helps,
>
> -Andi
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:[~2004-08-07 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2q0Wb-2Tc-17@gated-at.bofh.it>
[not found] ` <2q1pe-3hq-17@gated-at.bofh.it>
[not found] ` <2qlo1-wO-37@gated-at.bofh.it>
2004-08-06 23:26 ` Is extern inline -> static inline OK? Andi Kleen
2004-08-07 1:26 ` Adrian Bunk [this message]
2004-08-06 0:39 Tim Bird
2004-08-06 0:58 ` H. Peter Anvin
2004-08-06 22:29 ` Tim Bird
2004-08-06 22:29 ` H. Peter Anvin
[not found] ` <20040806070027.GA20642@twiddle.net>
2004-08-06 18:57 ` Tim Bird
2004-08-07 2:41 ` Richard Henderson
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=20040807012614.GC17708@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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.