On Mon, 18 Sep 2000, David Woodhouse wrote:
> 
> [EMAIL PROTECTED] said:
> >  Note that with most versions of gcc this is all a complete non-issue,
> > as most versions of gcc will _always_ inline a function that the user
> > has asked to be inlined. So the issue seldom actually comes up.
> 
> I thought that 'extern inline' was in fact the intended usage. That way, if 
> gcc decides it's not going to obey our explicit instruction to inline a 
> certain function, we get to know about it.

And what could we do about it? Basically nothing.

So we might as well use "static inline".

                Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Reply via email to