Re: -ffreestanding or not -ffreestanding
From: Roman Zippel
Date: Wed May 21 2008 - 07:46:20 EST
On Wed, 21 May 2008, Adrian Bunk wrote:
> Can we try to get this sorted out properly instead of constantly
> fiddling with it?
> Currently we use -ffreestanding on some architectures and fix breakages
> on the other architectures when they arise.
This won't help completely unless you also clean up all archs to use the
same mappings to the builtin functions.
The main problem I had with -ffreestanding is that it's awkward to map a
library function to the builtin function and also provide the fallback
If you look at asm-m68k/string.h I once tried this with the mem* functions
and I still have the duplicated memcmp in arch/m68k/lib/string.c.
(You could argue that it would be easier to just remove the define for
memcmp in this specific case, but I'm interested in the general case.)
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/