> 3) We could also try turning off this particular optimization
> (-fno-builtin perhaps) on this file, and not worry about it.
In particular, it would probably make sense for the kernel to use
-ffreestanding (which implies -fno-builtin) throughout then selectively
enable the built-in functions that are wanted with macros such as
#define strcpy(d, s) __builtin_strcpy((d), (s))
in an appropriate header, then #undef these macros in the files that
shouldn't use the built-in functions.
-- Joseph S. Myers jsm28@cam.ac.uk- 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/