As a 'beta tester' I'd like to relay a few more of my experiences.

With the compilation of gcc-2.7.0 I for the first time witnessed
instabilities in the NetBSD-port. I would not be surprised if the
majority -if not all - of the problems are due to faulty disk I/O.

Currently I am busy building the third stage of the gcc compiler.
I used -g -O2 -fomit-frame-pointer as compiler options.
So far none of the makes made it through, there always was some
crash. But after the crash the same code compiled flawlessly, 
which means that its a kernel problem (IMO).

Crashes witnessed:

   two or three times, machine freezes harddisk light stays ON
   
   address kernel panic (UNLK A6), probably some stack messup
   
   cc1 exited because of signal 6 (Abort I think)
   
Compilation is __slow__. Although I do have Blowup installed, 
I am not really using it, I usually run with a conservative 16/32 
(normal) sometimes 18/36 setting. Once a compile file took 16 Minutes!!
Raytracing is faster than gcc :)

I think the Linux port was also plagued with Falcon SCSI problems, 
and they finally fixed their driver. Maybe one could take a few hints
from their source ?

That's it for now.

Nat!


  
------------------"Bang that bit that doesn't bang"---------------

                 Yeah, money talks / ... I should know
                  Mine always says / 'Good bye'!
                                                    David Lee Roth