Re: kernel-2.2.1-undefined references.
H. Peter Anvin (hpa@transmeta.com)
7 Feb 1999 07:03:08 GMT
Followup to: <m108lCi-0007U2C@the-village.bc.nu>
By author: alan@lxorguk.ukuu.org.uk (Alan Cox)
In newsgroup: linux.dev.kernel
>
> > NB, the "static inline" solution may mean that, for example, both
> > tcp_input.o and tcp_output.o might have explicit code for skb_push() or
> > whatever, but as these functions usually are quite small and (since they're
> > declared static) they don't bite each other, IMHO that's not a problem.
>
> At this point egcs really needs to invent a new "common inline" of some sort.
> There are kernel cases where you need to force inlining and where you don't
> want duplicated code all over the place caused by compiler weaknesses.
>
> Granted talk is cheap, Im not an egcs hacker.
>
"extern inline" is what you want. The problem is that it doesn't work
without -O (*this* is the compiler misfeature!) but the Linux kernel
won't compile that way, either...
-hpa
--
"Linux is a very complete and sophisticated operating system. There
are, and will be, large numbers of applications available for it."
-- Paul Maritz, Group Vice President for Platforms And Applications,
Microsoft Corporation [Reference at: http://www.kernel.org/~hpa/ms.html]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/