On Jul 3 2014, Uros Bizjak wrote:
Maybe a new hook should be introduced instead: TARGET_IEEE_FORMAT_P
(mode). For some targets, even soft-fp supports required rounding
modes and can generate exceptions.
Before doing anything, it would be a good idea to decide on what IEEE
conformance means. T
On Thu, Jul 3, 2014 at 9:14 AM, Uros Bizjak wrote:
> On Wed, Jul 2, 2014 at 11:13 PM, FX wrote:
>> I’ve recently added IEEE support for the Fortran front-end and library. As
>> part of that, the front-end should be able to determine which of the
>> available floating-point types are IEEE-confor
On Wed, Jul 2, 2014 at 11:13 PM, FX wrote:
> I’ve recently added IEEE support for the Fortran front-end and library. As
> part of that, the front-end should be able to determine which of the
> available floating-point types are IEEE-conforming [1]. Right now, I’ve taken
> a conservative approac
I’ve recently added IEEE support for the Fortran front-end and library. As part
of that, the front-end should be able to determine which of the available
floating-point types are IEEE-conforming [1]. Right now, I’ve taken a
conservative approach and only considered the target’s float_type_node a
