> IMHO omitting -fno-builtin when compiling the kernel was always a risky
> proposition... Since we provide our own copies of many of the builtins
> [which are used in the kernel] anyway... why not always -fno-builtin,
> and then call __builtin_foo when we really want the compiler's version..
That may well be the right thing to do. Of course we rely on the compiler
providing some of them too
> gcc 3.0 without -fno-builtin is perfectly allowed to assume it can
> insert calls to memcpy..
I have no argument about its correctness there, but -fno-builtin will still
give a kernel that dosnt link due to abs() and other problems.. 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
