Re: [2.6 patch] include/linux/bio.h: "extern inline" -> "static inline"

[Kimball Murray <kmurray@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

Jens Axboe wrote:

>On Tue, Jul 26 2005, Adrian Bunk wrote:
>  
>
>>"extern inline" doesn't make much sense.
>>    
>>
>
>Yep, thanks.
>
>  
>
IIRC, there was a time when the extern inline construct was used to 
catch cases where the compiler did not inline the function (you'd get a 
link error).  Seems like it still works.  Try building the attached 
files in each of the following ways:

gcc -o foo foo.c

    and

gcc -O2 -o foo foo.c

In the first case, you get a link error, because there is no inlining.

-kimball

[-- Attachment #2: foo.c --]
[-- Type: text/plain, Size: 102 bytes --]

#include "bar.h"

void foo(void) {
	bar();
}

int main(int argc, char *argv[])
{
	foo();
	return 0;
}

[-- Attachment #3: bar.h --]
[-- Type: text/plain, Size: 33 bytes --]

extern inline void bar(void)
{
}