(j3.2006) IEEE and the GPU world
Van Snyder
Van.Snyder
Wed Aug 18 21:30:41 EDT 2010
On Wed, 2010-08-18 at 18:06 -0700, Malcolm Cohen wrote:
> Van Snyder wrote:
> > "scoping unit" should be "scope" throughout Clause 14 since we don't want to
> > require IEEE compliance within an entire scoping unit if there is a USE
> > statement for an IEEE module within a BLOCK construct.
>
> A BLOCK construct is a scoping unit, so that wouldn't do anything.
Malcolm is right. I somehow managed to be looking at 09-007r3 when I
composed the message.
> > If we use "scope" throughout Clause 14, one could have a USE statement for an
> > IEEE module in a scope, and then declare an entity of the same name within a
> > BLOCK construct within that scope, thereby "turning off" IEEE features within
> > that block -- where you might want to use a GPU to do some arithmetic.
This was clearly wrong.
> 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.
>
> Cheers,
More information about the J3
mailing list