Hi,
Peter Seebach wrote:

>can anyone point me at a fairly recent cc1 that doesn't get signal 10
>all the time?

>It dumps on telnetd/slc.c and (uh-oh) on common/bi-arity.c in gcc.

I own a CyberSCSI (mk1).  Some months ago, I kept trying to run
NetBSD-1.2 on IDE partitions but I consistently encountered
"random" signals when doing compilations (trying to make
bash-2.0, actually).
Recently, I could repeatedly run the same compilations without
any trouble... while I had the (Cyber)SCSI module removed from
the CyberStorm !

My conclusion is that unsupported hardware can cause undesirable
signals, probably because some hardware interrupts aren't
properly handled and acknowledged (someone correct me if I'm
wrong...)

BTW, since I make a heavy use of my CyberSCSI, I cannot afford
keeping it out of my A4000... So I have temporarily stopped
trying NetBSD because it won't work on my harware... :-(

Wouldn't it be sensible to have some fake support of such
hardware ? Or in other words, to have such hardware friendly
ignored (its interrupts being gently handled with No Operation ?)
This way, I could eventually use NetBSD on IDE, and who knows,
maybe I could contribute supporting my favorite hardware ?!...

Jerome

-- 
"Owing to circumstances over which the management of the hall
 had no control, tonight's program will be given exactly as
 advertised..." (G.Hoffnung)