Re: removing bcopy... because it's half broken

[Arjan van de Ven]

On Tue, 2005-01-11 at 11:10 +0100, Bastian Blank wrote:
> On Sun, Jan 09, 2005 at 12:42:42PM -0800, Linus Torvalds wrote:
> > On Sun, 9 Jan 2005, Christoph Hellwig wrote:
> > > We're building with -ffreestanding now, so gcc isn't allowed to emit
> > > any calls to standard library functions.
> > Bzzt. It still emits calls to libgcc. 
> 
> Yes. This means IMHO that the image and every module needs to link
> against libgcc to include the required symbols. It is rather annoying to
> see modules asking for libgcc symbols.

I disagree with your first sentence: The kernel provides the required
symbols (bcopy is special here, it no longer gets emitted by gcc since
like gcc version 2.6); the ones the kernel does NOT provide are
generally undesirable in kernel spec, eg floating point and 64 bit
divisions...


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/