> Being different is not fine if it changes gcc behavior.  We don't
> provide netbsd-cc on boxes.  We provide something claiming to be
> "gcc".

But hasn't it been hacked on in NetBSD-specific ways already?  That is,
don't we already apply NetBSD-specific patches to it when rolling in a
new gcc?

If fixing this bug would be seen as unwarranted modification of the
compiler, then the only choice I see is to back off to an earlier
compiler, before the bug went in.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B