Xref: utzoo comp.sys.att:12166 comp.lang.c:38487
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsh!daw
From: daw@cbnewsh.att.com (David Wolverton)
Newsgroups: comp.sys.att,comp.lang.c
Subject: Re: Strange Behavior -- AT&T Std C
Message-ID: <1991Apr19.180625.9141@cbnewsh.att.com>
Date: 19 Apr 91 18:06:25 GMT
References: <1991Apr18.144759.4492@mccc.edu>
Followup-To: comp.sys.att,comp.lang.c
Distribution: usa
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 16

In article <1991Apr18.144759.4492@mccc.edu>, pjh@mccc.edu (Peter J. Holsberg) writes:
> Here's the source:
	[lots deleted]

If your system is using IEEE 754-based floating point (which
has a good probability of being true), then it is possible
to ask the floating point subsystem to signal several types
of f.p. exceptions, including "inexact" (that is, that a
computation had to round off a result).  Normally, you would
never want to enable this particular signal, but if it was
enabled, it would probably fire on ANY call to exp(), because
it would be very unlikely that exp()'s internal computations
would be completely roundoff-free.

Dave Wolverton
daw@honshu.att.com