This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: [ruediger.franke@de.abb.com: 1.1.0: wrong negative HUGE_VAL]
- To: Chris Faylor <cgf at cygnus dot com>, cygwin-developers at sourceware dot cygnus dot com
- Subject: RE: [ruediger.franke@de.abb.com: 1.1.0: wrong negative HUGE_VAL]
- From: "Parker, Ron" <rdparker at butlermfg dot com>
- Date: Fri, 9 Jun 2000 13:37:37 -0500
> Anyone know anything about HUGE_VAL?
I only have my copy of the C++ standard it references the C standard on this
and my copy of it is at home. So, you get my opinion. ISTM that on a
machine which uses IEEE floating point infinity is the correct value for
HUGE_VAL. Supporting this is the glibc manual which says:
<<Macro: double HUGE_VAL
An expression representing a particular very large number. On machines that
use IEEE floating point format, the value is "infinity". On other machines,
it's typically the largest positive number that can be represented.
The value of this macro is used as the return value from various
mathematical functions in overflow situations.>>
This is quoted from
http://www.cs.utah.edu/dept/old/texinfo/glibc-manual-0.02/library_17.html#ID
X1249.
IIRC the only time the IA32 FPU is not IEEE standard is when using 80-bit
floating point values and cygwin doesn't even use those values for 'long
double' because of some MS libraries or DLL's.
It seems that the __infinity variable is not being properly set, I am
looking now...
application/ms-tnef