Re: [2.6 patch] blackfin: "extern inline" -> "static inline"

["Mike Frysinger" <vapier.adi@gmail.com>]

On 10/25/07, H. Peter Anvin <hpa@zytor.com> wrote:
> Mike Frysinger wrote:
> >> Do you have any example for your claim "to get gcc to not inline things
> >> when building debug versions"?
> >
> > $ cat test.c
> > __attribute__((always_inline)) int foo(void) { return 0; }
> > int main(void){ return foo(); }
> > $ gcc -g test.c -o test
> > $ readelf -s test | grep FUNC | grep -v _
> >     61: 00000000004004b8    11 FUNC    GLOBAL DEFAULT   13 foo
> >     68: 00000000004004c3    11 FUNC    GLOBAL DEFAULT   13 main
> >
> > looks pretty straightforward to me
>
> For "debug version" meaning -O0, this is true.

which is what i meant, sorry for not being more clear

anyways, this is all moot ... we dont want "always inline" nor do we
want "static inline" for our string functions.  we want the classical
GNU meaning of "extern inline" which means we're going to either have
a Blackfin specific "extern_inline" define or we get one added to the
common compiler headers and use that.

Peter (or is it "H. Peter" ?): you going to post a patch or should i ?
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/