On Sat, 5 Jun 1999, NetBSD Mailing list wrote:

> > This is the first time I've ever seen an internal compiler error quite
> > like the one that follows.  (Mmmmmm Lispy).

> I've seen this a number of times.  Not sure if it exists because of
> compiler errors or what, but I end up getting around it by turning off
> optimisation (remove the -O).

I was given the tip to use either the -O2 or -frerun-cse-after-loop
option.  I found that -O2 worked out alright for my particular instance.

-brian.
---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!