Re: KA655 Kernel Compile and Corrupt Object Files

> TL;DR: gcc produces corrupted kernel object files on a diskless, hardware KA$

Do you have any particular reason to believe the hardware is not
broken?  Slightly broken hardware can cause no end of bizarre symptoms.

Certainly if the real thing differs from a simulator, the simulator is
not an accurate simulation...of that thing.  But, in the case of simh,
I am inclined to consider the simulation probably-correct enough that
broken hardware becomes one of the most plausible explanations, to me.

> Compiling the 10.1 kernel sources under NetBSD 10.1 on a KA655 w/32MB RAM (1$

> * It's funny... for comparison, I swear I saw a 25MHz (or so) 68030 Macintos$

That strikes me as very plausible.  I suspect the major reasons for the
difference are that 10.1 gcc is far more of a resource pig than 1995
gcc and 10.1's kernel is sigificantly larger than 1995 kernels (in
terms of functionality, not necessarily bytes).

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		[email protected]
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B