X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Thu, 8 Apr 1999 18:02:51 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Patches for <errno.h> and <float.h> for C9X standard compatibility
In-Reply-To:	<001d01be81d8$802ceee0$8a033bd4@default>
Message-ID:	<Pine.LNX.3.93.990408175936.200a-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 8 Apr 1999, Laurynas Biveinis wrote:

> I am not sure what value should be defined for
> FLT_EVAL_METHOD. Posibilities are:
> 
> -1 indeterminable;
> 
> 0 evaluate all operations and constants just to the range and precision of
> the type;
> 
> 1 evaluate operations and constants of type float and double to the range
> and
> precision of the double type, evaluate long double operations and
> constants to the range and precision of the long double type;
> 
> 2 evaluate all operations and constants to the range and precision of the
> long
> double type.

For the x86 FPUs in normal state, '2' is the correct choice, I think.
They evaluate everything in 'long double' (80 bits) precision, and convert
to double only when values are stored to file. 

What about diffs to the libc docs? There is documentation for the existing
errno values, somewhere, isn't there?

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -