From: Scott Wood <[EMAIL PROTECTED]> Date: Fri, 02 May 2008 16:45:45 -0500
> David Miller wrote: > > If you link in libgcc, all of a sudden you have a whole new class of > > potential problems, don't do it. > > > > All it takes is one of these libgcc libcalls the kernel actually > > references, needing something else in libc, to make this exercise > > futile. > > What in libgcc references libc, and why isn't this a problem for > Linux/ARM, Linux/SH, U-boot, and the many other libc-less programs that > use libgcc? The problem only occurs once you reference a function that references libc stuff, and those guys are just lucky so far. It's also one less variable to debug if you put the implementation in the kernel, or do you like debugging compiler induced problems? I don't :-) _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
