public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is extern inline -> static inline OK?
Date: Fri, 06 Aug 2004 15:29:23 -0700	[thread overview]
Message-ID: <41140643.70704@zytor.com> (raw)
In-Reply-To: <41140654.3060609@am.sony.com>

Tim Bird wrote:
> 
> Thanks!
> 
>  From what I have read, for either 'extern inline' or 'static inline'
> the compiler is free to not inline the code. Is this wrong?
> 
> It is my understanding that...
> In the 'static inline' case the compiler may create a function in the
> local compilation unit. But in the 'extern inline' case an extern
> non-inline function must exist. If the compiler decides not to inline
> the function, and a non-inline function does not exist, you get a linker
> error.  Are you saying that, therefore, 'extern inline' functions are
> used (without definition of extern non-inline functions to back them)
> in order to guarantee that NO non-inline version of the function exists?
> 

Yes; the final link will fail with an undefined symbol if "extern inline" 
fails to inline.

	-=hpa

  reply	other threads:[~2004-08-06 22:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06  0:39 Is extern inline -> static inline OK? 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 [this message]
     [not found] ` <20040806070027.GA20642@twiddle.net>
2004-08-06 18:57   ` Tim Bird
2004-08-07  2:41     ` Richard Henderson
     [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     ` Andi Kleen
2004-08-07  1:26       ` Adrian Bunk

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=41140643.70704@zytor.com \
    --to=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox