Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!usenet!prism!bostrov
From: bostrov@prism.cs.orst.edu (Vareck Bostrom)
Newsgroups: comp.sys.next
Subject: Um, bug report?
Summary: Whiler ray-tracing my system locked
Keywords: 68040 fp bug?
Message-ID: <1991Apr12.152419.16129@lynx.CS.ORST.EDU>
Date: 12 Apr 91 15:24:19 GMT
Sender: @lynx.CS.ORST.EDU
Organization: Oregon State University, Computer Science Dept
Lines: 20
Nntp-Posting-Host: prism.cs.orst.edu

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