This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: expand and truncate and 387
- To: moshier at mediaone dot net, Richard Henderson <rth at cygnus dot com>
- Subject: Re: expand and truncate and 387
- From: Richard Henderson <rth at cygnus dot com>
- Date: Mon, 30 Nov 1998 19:28:27 -0800
- Cc: Jan Hubicka <hubicka at atrey dot karlin dot mff dot cuni dot cz>, law at cygnus dot com, egcs at cygnus dot com, Marc Lehmann <pcg at goof dot com>
- References: <19981130171931.A22081@dot.cygnus.com> <Pine.LNX.4.05.9811302127001.6760-100000@moshier.ne.mediaone.net>
- Reply-To: Richard Henderson <rth at cygnus dot com>
On Mon, Nov 30, 1998 at 09:30:41PM -0500, Stephen L Moshier wrote:
>
> Therefore no additional signaling is
> required when the value is already in a register.
>
> Therefore? Suppose the value was loaded for some other operation,
> then the user clears the IEEE flags, then calls for a conversion operation
> on the value that is still in the register. Mustn't there be
> another exception, on the conversion?
I sure _hope_ the user ain't fooling aroung with exception flags
behind my back with asms.
If they do things properly, they'll be making a function call
to feclearexcept (iso c9x <fenv.h>). And since all fp regs
are call-clobbered, there will be no values live in registers.
r~