From: Dan Nagle <danlnagle@me.com>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: Damian Rouson <damian@sourceryinstitute.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: Coarrays and -fdefault-integer-8
Date: Sun, 11 Mar 2018 17:27:00 -0000 [thread overview]
Message-ID: <D927DFDC-B48C-4691-9A5A-846266228002@me.com> (raw)
In-Reply-To: <83E21824-A3AB-4EEE-BB84-16468EE56CD0@lps.ens.fr>
Hi,
A question occurring to me after I posted is,
Does -fdefault-integer-8 change the values of atomic_int_kind and atomic_logical_kind ?
I suppose the answer may be hardware-dependent.
> On Mar 11, 2018, at 10:57 , Dominique d'Humières <dominiq@lps.ens.fr> wrote:
>
> OK, thanks.
>
> Dominique
>
>> Le 11 mars 2018 à 17:33, Dan Nagle <danlnagle@me.com> a écrit :
>>
>> Hi,
>>
>> Pardon me for answering a question for Damian,
>>
>>> On Mar 11, 2018, at 05:37 , Dominique d'Humières <dominiq@lps.ens.fr> wrote:
>>>
>>
>>> Is is expected that the arguments of atomic_* have to be INTEGER(4)/LOGICAL(4) (atomic_int_kind)?
>>
>> atomic_add atom must be of atomic_int_kind
>> atomic_and atom must be of atomic_int_kind
>> atomic_cas atom may be of atomic_Int_kind or atomic_logical_kind
>> atomic_define atom may be of atomic_int_kind or atomic_logical_kind
>> atomic_fetch_add atom must be of atomic_int_kind
>> atomic_fetch_and atom must be of atomic_int_kind
>> atomic_fetch_or atom must be of atomic_int_kind
>> atomic_fetch_xor atom must be of atomic_int_kind
>> atomic_or atom must be of atomic_int_kind
>> atomic_ref atom may be of atomic_int_kind or atomic_logical_kind
>> atomic_xor atom must be of atomic_int_kind
>>
>> from 1539-1 2017 (17-007r1) pg 356 - 360 HTH
>>
>> --
>>
>> Cheers!
>> Dan Nagle
>>
>
--
Cheers!
Dan Nagle
next prev parent reply other threads:[~2018-03-11 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 11:37 Dominique d'Humières
2018-03-11 16:34 ` Dan Nagle
2018-03-11 16:57 ` Dominique d'Humières
2018-03-11 17:27 ` Dan Nagle [this message]
2018-03-11 18:03 ` Dominique d'Humières
2018-03-11 18:20 ` N.M. Maclaren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D927DFDC-B48C-4691-9A5A-846266228002@me.com \
--to=danlnagle@me.com \
--cc=damian@sourceryinstitute.org \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).