SH optimized software floating point routines

Joseph S. Myers joseph@codesourcery.com
Fri Jul 23 09:02:00 GMT 2010


On Thu, 22 Jul 2010, Joern Rennecke wrote:

> Quoting "Joseph S. Myers" <joseph@codesourcery.com>:
> 
> > That diff does not appear to relate to undefined behavior.  GCC considers
> > these out-of-range conversions to yield an unspecified value, possibly
> > raising an exception, as per Annex F, and does not take the liberty of
> > optimizing on the basis of them being undefined when not in an IEEE mode.
> 
> Well, still, the test is wrong in possibly raising an exception there,
> with no provisions to ignore the exception or catch any signal raised.

The expectation is that floating-point exceptions will not trap by 
default, again in accordance with Annex F even when not in an IEEE mode.

-- 
Joseph S. Myers
joseph@codesourcery.com



More information about the Gcc mailing list