Messages in this thread | | | Date | Tue, 22 Aug 2006 00:58:37 +0200 | From | Adrian Bunk <> | Subject | Re: [2.6 patch] re-add -ffreestanding |
| |
On Tue, Aug 22, 2006 at 12:27:28AM +0200, Andi Kleen wrote: > > > It disables the automatic usage of builtins which is OK. > > No, it's not ok -- it is the problem. We want to use the builtins.
Without -ffreestanding, the compiler is completely free to decide whether to use a builtin or whether to not use it - and which other C library functions to use.
Your commit 6edfba1b33c701108717f4e036320fc39abe1912 that claimed "it was only added for x86-64, so dropping it should be safe" was not safe, it had broken at least mips and m68k. This wrong justification alone should warrant a revert of this commit.
What's the problem with adding -ffreestanding and stating explicitely which functions we want to be handled be builtins, and which functions we don't want to be handled by builtins?
This looks like the right way to go instead of breaking other architectures here and there.
> -Andi
cu Adrian
--
Gentoo kernels are 42 times more popular than SUSE kernels among KLive users (a service by SUSE contractor Andrea Arcangeli that gathers data about kernels from many users worldwide).
There are three kinds of lies: Lies, Damn Lies, and Statistics. Benjamin Disraeli
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |