(j3.2006) STAT= and integer kind

[Bader, Reinhold]

Hello Tobias, 

Not adding STAT to ATOMIC_CAS was an oversight of mine, sorry. I was too focused on getting the
separation of the op/fetch_op right. The ATOMIC_CAS doesn't require a FETCH variant, but of course
does need to have the STAT added. Since there was agreement to generally add STAT, one could consider
fixing this an editorial issue, I suppose.

Cheers 
Reinhold

>-----Urspr?ngliche Nachricht-----
>Von: j3-bounces at mailman.j3-fortran.org [mailto:j3-bounces at mailman.j3-
>fortran.org] Im Auftrag von Tobias Burnus
>Gesendet: Dienstag, 8. Juli 2014 07:39
>An: j3 at mailman.j3-fortran.org
>Betreff: Re: (j3.2006) STAT= and integer kind
>
>Bill Long wrote:
>> I agree with Malcolm's comments, particularly about the last one
>> regarding minimal requirements on the sizes of integers appropriate
>> for STAT arguments in intrinsics. I will be putting the text from the
>> meeting papers into the next TS draft, including having default
>> integer STAT arguments.
>
>I also concur with the comment. I think many implementations will have a stat
>value which does not fit into a 8byte-variable. If you use "default integer" in
>the TS draft, we are back at consistency; I don't intent to implement
>extensions before F2015.
>
>Regarding the atomic intrinsics and STAT: Is there a specific reason that
>ATOMIC_CAS does not have a STAT argument? At least J3/14-173r2 doesn't
>list ATOMIC_CAS, contrary to the new atomic_[fetch_]op (op = add, and, or,
>xor) and the old atomic_ref/atomic_define.
>
>Tobias
>_______________________________________________
>J3 mailing list
>J3 at mailman.j3-fortran.org
>http://mailman.j3-fortran.org/mailman/listinfo/j3