🚀 go-pugleaf

>
>   To save me (and possibly you/others) relearning the wheel (the HARD way)
>   could somebody drop the net a pointer to a list of know compiler bugs (etc)
>

Beat hard upon your distributor  there is a public, published bug list
from INMOS for all their software products. It took me about half a year
to get it out of parsytec (by that time I had found three serious code
generation bugs in the occam compiler, two of which were documented).

There was indeed a bug in the compiler with the return value of functions,
which turned up in two cases: more than 3 return arguments of one type
(overflow of the register stack, but caller and callee part of the code
generator had different ideas of what to do in that case); the RETURN
line itself called a function returning, eg, a float  the compiler
doesn't distinguish properly between the integer and floating evaluation
stack. A victim of that last bug is the wellknown function RAN 
as supplied with the compiler, it will never work!

But I haven't had the compiler complain in such a way as you report 
maybe you're lucky, because I spent days trying to find out what went
wrong, including looking at the disassembled code.
(The numbers after the error, BTW, are first an error number you can
look up in the manual and then an errorspecific number of which there
is exactly no docuumentation in all cases :))

Good hunting, Jan

jan@neuroinformatik.ruhrunibochum.de