bostrov@prism.cs.orst.edu (Vareck Bostrom) (04/12/91)
While ray-tracing last night (dkbtracer2.0, from skinner.cs.uoregon.edu) I realized that I hadn't compiled with the -O option, optimization. The tracer that I used was working fine up till then. I reMAKEd it with -O and started the tracer again. It appeared to be working much faster. It hit line 33 of 256 and the machine locked up. REALLY locked up. Command Command anything wouldn't work. The Power switch wouldn't work. I eventually had to jiggle the power cable. Where do I report bugs? Oh, it works fine withoug optimization. I don't understand what it's up to. It also works fine with optimization on 68030 cubes and SPARCstation 2's. (BTW, NeXT 040 appears about 1/3 to 1/2 the speed of a SPARCstation 2 in this application)_. Any ideas what could be the problem? How to fix it? Should I report it to NeXT and how would I do that? -- Vareck Bostrom bostrov@gnu.ai.mit.edu
madler@nntp-server.caltech.edu (Mark Adler) (04/13/91)
>> It hit line 33 of 256 and the machine locked up. REALLY locked up. Command
It's that bug in the Motorola fpu code in 2.0. Fixed in 2.1.
Mark Adler
madler@pooh.caltech.edu