[lkml]   [1999]   [Sep]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Possible GCC contamination of Linux
On Tue, 21 Sep 1999, Richard B. Johnson wrote:

>memcpy() and other routines that can be optimized for certain CPUs are
>in the architecture-specific directories. The only built-in being used
>that I found was abs().
>I'll wait for the next clean Linux release and submit a patch.

IMHO there's nothing to change into the kernel.

I don't care at all how my gcc is been compiled for, the gcc output _must_
be the same for all GCC of such same version careless about which
optimizations are been used to compile gcc itself. The makefiles must
ensure that the libgcc is been compiled for i386 and the gcc build process
may also create a different libgcc.a for each different architecture
supported by gcc and then link the right one statically into the binary in
function of the flag specifyed to the gcc executable.

The output of gcc must be the same even if I'm cross compiling the kernel
for i386 on an Alpha. If I choose -march=386 and some 686 assembler goes
into the binary then gcc is definitly buggy and must be fixed.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:54    [W:0.102 / U:0.644 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site