public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andre Vehreschild <vehre@gmx.de>
To: Jerry DeLisle <jvdelisle@charter.net>,GCC-Patches-ML
	<gcc-patches@gcc.gnu.org>,GCC-Fortran-ML <fortran@gcc.gnu.org>
Subject: Re: PING! [PATCH, Fortran, accaf, v1] Add caf-API-calls to asynchronously handle allocatable components in derived type coarrays.
Date: Tue, 29 Nov 2016 23:43:00 -0000	[thread overview]
Message-ID: <E6A0D123-9EDE-48B6-AC3A-39A62736D7F2@gmx.de> (raw)
In-Reply-To: <692b78e8-c237-7355-ce8b-38cfac0acfa3@charter.net>

Hi Jerry,

Tests with multiple images go into the opencoarrays testsuite. Still to push though. The tests I have so far all pass.

- Andre

Am 30. November 2016 00:06:22 MEZ, schrieb Jerry DeLisle <jvdelisle@charter.net>:
>On 11/28/2016 10:33 AM, Andre Vehreschild wrote:
>> PING!
>>
>> I know it's a lengthy patch, but comments would be nice anyway.
>>
>> - Andre
>>
>> On Tue, 22 Nov 2016 20:46:50 +0100
>> Andre Vehreschild <vehre@gmx.de> wrote:
>>
>>> Hi all,
>>>
>>> attached patch addresses the need of extending the API of the
>caf-libs to
>>> enable allocatable components asynchronous allocation. Allocatable
>components
>>> in derived type coarrays are different from regular coarrays or
>coarrayed
>>> components. The latter have to be allocated on all images or on
>none.
>>> Furthermore is the allocation a point of synchronisation.
>>>
>>> For allocatable components the F2008 allows to have some allocated
>on some
>>> images and on others not. Furthermore is the registration with the
>caf-lib,
>>> that an allocatable component is present in a derived type coarray
>no longer a
>>> synchronisation point. To implement these features two new types of
>coarray
>>> registration have been introduced. The first one just registering
>the
>>> component with the caf-lib and the latter doing the allocate.
>Furthermore has
>>> the caf-API been extended to provide a query function to learn about
>the
>>> allocation status of a component on a remote image.
>>>
>>> Sorry, that the patch is rather lengthy. Most of this is due to the
>>> structure_alloc_comps' signature change. The routine and its
>wrappers are used
>>> rather often which needed the appropriate changes.
>>>
>>> I know I left two or three TODOs in the patch to remind me of things
>I have to
>>> investigate further. For the current state these TODOs are no reason
>to hold
>>> back the patch. The third party library opencoarrays implements the
>mpi-part
>>> of the caf-model and will change in sync. It would of course be
>advantageous
>>> to just have to say: With gcc-7 gfortran implements allocatable
>components in
>>> derived coarrays nearly completely.
>>>
>>> I know we are in stage 3. But the patch bootstraps and regtests ok
>on
>>> x86_64-linux/F23. So, is it ok for trunk or shall it go to 7.2?
>>>
>>> Regards,
>>> 	Andre
>>
>>
>
>Patch applies OK, regression tested OK here, test cases look
>reasonable. Have 
>you been able to test with multiple images?
>
>Jerry

-- 
Andre Vehreschild * Kreuzherrenstr. 8 * 52062 Aachen
Tel.: +49 241 929 10 18 * vehre@gmx.de

  reply	other threads:[~2016-11-29 23:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 19:47 Andre Vehreschild
2016-11-28 18:33 ` PING! " Andre Vehreschild
2016-11-29 23:06   ` Jerry DeLisle
2016-11-29 23:43     ` Andre Vehreschild [this message]
2016-11-30  6:49   ` Paul Richard Thomas
2016-11-30 13:30     ` Andre Vehreschild
2016-11-30 13:48       ` Janus Weil
2016-11-30 14:23         ` Andre Vehreschild
2016-11-30 14:35           ` Andre Vehreschild
2016-11-30 14:53             ` Janus Weil
2016-11-30 15:59               ` Andre Vehreschild
2016-12-01  9:55                 ` Andre Vehreschild

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=E6A0D123-9EDE-48B6-AC3A-39A62736D7F2@gmx.de \
    --to=vehre@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle@charter.net \
    /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).