(j3.2006) IEEE and the GPU world

[Malcolm Cohen]

John Reid wrote:
> Malcolm Cohen wrote:
>> As I read John's suggested interpretation, both USE and HOST association 
>> "turn off" IEEE compliance.
>>
>> I really don't think this is acceptable.  (And doesn't make sense for 
>> IEEE_FEATURES.)
>>
>> Maybe I have just misunderstood it, but... that's what the words seem to say.
>
> The present words (14.1:p3) are
> "If a scoping unit does not access IEEE_FEATURES, IEEE_EXCEPTIONS, or
> IEEE_ARITHMETIC, the level of support is processor dependent, and need
> not include support for any exceptions."
> and Fortran 2003 has the same words.

So what.  That access might be via use (more than one USE) or host association.

> Thus an internal procedure that does nothing with the IEEE features might be 
> implemented on a GPU. It might be a surprise, but that's what the standard 
> says.

No it does not.

For example,
  "If a scoping unit has access to IEEE_DATATYPE of IEEE_FEATURES, within the 
scoping unit the processor shall support IEEE arithmetic etc."

This specifies that it works across both use and host association!

> However, I don't think this should be extended to blocks.

These should act the same as internal procedures, which they do as it is 
currently written.

You seem to have misread "access" as "reference".  They are not the same!

Cheers,
-- 
................................Malcolm Cohen, Nihon NAG, Tokyo.