public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] Update atomics support for TS18508
Date: Sat, 12 Jul 2014 18:44:00 -0000	[thread overview]
Message-ID: <CAGkQGiJdhLzqW2RW+0wSNYLOEi7VYrtWx_fRZBTzyVHbbcRBUA@mail.gmail.com> (raw)
In-Reply-To: <53C0576A.3080001@net-b.de>

Dear Tobias,

OK for trunk.

Thanks for the patch.

Paul

On 11 July 2014 23:30, Tobias Burnus <burnus@net-b.de> wrote:
> This patch updates the atomic support for TS18508, namely:
> – The atomic intrinsics now take a STAT= argument
> – Add the new atomics atomic_{add,and,or,xor} and their fetch variants
> atomic_fetch_{add,and,or,xor} – and compare and swap (atomic_cas)
>
> In addition, the previous implementation (for -fcoarray=single) used simple
> assignments; the patch changes those to using real atomic operations, which
> makes the atomic operations thread safe.
>
> Build and regtested on x86-64-gnu-linux.
> OK for the trunk?
>
>
> As next step, library calls have to be added for -fcoarray=lib. For
> coarrays, I also a have still on my to do list: Adding a type-conversion
> test case for -fcorray=lib; implementing in the library the support for
> vector subscripts; and fixing an issue with nonallocatable polymorphic dummy
> coarrays and select type.
> For full F2008 support, the following is needed as well: locking and
> critical blocks – and allocatable/pointer components of derived types. For
> TS18508 much more is needed, in particular co_reduce/co_broadcast and team
> support.
>
> Tobias



-- 
The knack of flying is learning how to throw yourself at the ground and miss.
       --Hitchhikers Guide to the Galaxy

  reply	other threads:[~2014-07-12 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 21:30 Tobias Burnus
2014-07-12 18:44 ` Paul Richard Thomas [this message]
2014-07-13  7:58 ` Andreas Schwab
2014-07-13  7:53 Dominique Dhumieres

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=CAGkQGiJdhLzqW2RW+0wSNYLOEi7VYrtWx_fRZBTzyVHbbcRBUA@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).