Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!wupost!uunet!charon.amdahl.com!amdahl!JUTS!griffin!gab10
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] instlling fpu results in floating exceptions
Keywords: 387 fpu
Message-ID: <bdES02Kd2dLZ01@JUTS.ccc.amdahl.com>
Date: 5 Dec 92 06:15:49 GMT
References: <andre.27@maties.sun.ac.za> <1fdmseINN5i6@tricky.wft.stack.urc.tue.nl> <1992Dec3.205109.23160@mnemosyne.cs.du.edu> <1992Dec4.165217.907@cm.cf.ac.uk>
Sender: netnews@ccc.amdahl.com
Organization: Amdahl Corporation
Lines: 29
In article <1992Dec4.165217.907@cm.cf.ac.uk>, paul@myrddin.isl.cf.ac.uk
(Paul Richards) writes:
> In article <1992Dec3.205109.23160@mnemosyne.cs.du.edu>
> jlwright@nyx.cs.du.edu (Jason Wright) writes:
> >Hello all!
> > I've been experiencing the same troubles listed in previous posts.
> >I'm using a Cyrix 387 (for a 386-16 Don't laugh). cc1 kept exiting
> with
> >signal 6 as someone said was happeneing with the ULSI.
> > Anyone else had any trouble with the Cyrix 387SX chip? I'd like
> >(again, don't laugh) to get the mtv raytracer to run with the chip.
>
> I get these signal 6 errors with an INTEL 486 so I don't think it's
> related to the chip.
For me, the Signal 6 problem with cc1 and g++ turned out to be an invalid
constant in the include file math.h. The value of HUGE_VAL is quite a bit
too huge. They have alreay fixed this in newer releases. gcc 2.1 reported
a message (and then blew up).
In math.h, HUGE_VAL get defined to 1e500. It works if you set it to
1.7976931348623157E+308. There are also a few suspects in float.h.
If you get further problems, try isolating the offending source code and then
change the defines.
--
Gary Browning | Exhilaration is that feeling you get just after a
| great idea hits you, and just before you realize
| what is wrong with it.