lkml.org 
[lkml]   [1999]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Possible GCC contamination of Linux
On Mon, 20 Sep 1999, Richard B. Johnson wrote:

>
> Hello,
> I spent the weekend trying to track down the reason why Linux (any
> recent version), complied for a 486-SX (no FPU), will not boot.
> It crashes during startup, about the time it looks for a PCI bus.
>
> The C Compiler (version 2.8.1) was compiled on a i686 machine. If I
> recompile on a '486, it will generate a Linux image that boots okay.
>
> So it looks as though the C Compiler, compiled on a 686, generates 686
> machine-code instructions. I don't think this is the correct behavior
> because the gcc command-line contains -m486.
>
> So, is there the possibility that something from the gcc library gets
> linked into the kernel? If so, how would I prevent it from happening?

Probably bug in gcc. Please add -mcpu=i486 and recompile Linux kernel on
i686.
If works add this as workaround for i386 arch.

On gcc 2.95.1 on i586 -m486 is equivalent to -m486 -mcpu=i486

Wiget
--
__ __ _ _
/ / /\ \ (_) __ _ ___| |_ @__mail: Artur Frysiak
\ \/ \/ / |/ _` |/ _ \ __| Rudlice 10
\ /\ /| | (_| | __/ |_ 98-311 Ostrowek
\/ \/ |_|\__, |\___|\__|
|___/ email: Wiget@t17.ds.pwr.wroc.pl
PGP key: http://www.t17.ds.pwr.wroc.pl/~wiget/pgp.key
Fingerprint16 = 70 DB E0 2D 12 AB C7 31 B6 58 B5 61 B3 98 B6 E6

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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