public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Zaak Beekman <zbeekman@gmail.com>
Cc: Fortran List <fortran@gcc.gnu.org>
Subject: Re: [PATCH] Character length cleanup for Coarray Fortran library
Date: Sat, 10 Feb 2018 21:07:00 -0000	[thread overview]
Message-ID: <CAO9iq9EHev9zWW+iU6W-3hc27taKQ+Np_SER=XTV2gJXOMuxWA@mail.gmail.com> (raw)
In-Reply-To: <CAAbnBwYPbZVgmgOPTYOYv4n4iYYidUz0f+1qSDAazT4Zv6VnMQ@mail.gmail.com>

On Sat, Feb 10, 2018 at 9:25 PM, Zaak Beekman <zbeekman@gmail.com> wrote:
>>
>> Janne, I've scanned the patch and it appears to a
>> fairly straight foward mechanical s/int/size_t
>> (and similar for nodes).  OK to commit (although
>> you may want to wait for a response from Damain
>> or Izaak Beekman).
>>
>> As this breaks an ABI and we've broken it for 8.0,
>> I think this should go into trunk.  You may need
>> to ping Jakub or Richard for final approval.
>>
>> --
>> Steve
>>
>
> Hi Janne & Steve,
>
> I'm still getting used to the GFortran mailing list, and trying to get up
> to speed with your dev practices, so please bear with me.
>
> Also, let me add the caveat that, to date, I have mostly dealt with the
> OpenCoarrays build system and various project
> management/documentation/QA/CI and other administrivia and devops related
> stuff---I am not *super* intimately familiar with the actual code base and
> ABI. I am even less familiar with the GFortran inner workings. Alessandro
> Fanfarillo and Andre are certainly more knowledgeable than I am in this
> area.
>
> Is my understanding correct that I can just look at changes to caf_single.c
> and the header files to determine where the type changes will impact
> OpenCoarrays? A concise list of ABIs/APIs that need changes on the
> OpenCoarrays side would go a long way in helping us/me make the
> corresponding changes on the OpenCoarrays side. Also, this patch will only
> be merged into trunk, right? I.e., it will impact GFortran 8+, and not
> future releases on the 6 and 7 branches?

AFAICT, the change to libgfortran/caf/libcaf.h tells you what would be
necessary to change on the OpenCoarrays side. And yes, the idea would
be to push this change only to the 8 branch.

My problem is a bit the opposite of yours, namely that apart from
skimming through the github repo I have zero experience of
opencoarrays.

A related question (, not directed to you specifically), if anybody
happens to know: Is libgfortran/caf/mpi.c actually used by anything,
or is it some pre-OpenCoarrays attempt at creating an MPI runtime for
coarrays? In other words, can we remove it?




-- 
Janne Blomqvist

  parent reply	other threads:[~2018-02-10 21:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1518284822.56399.ezmlm@gcc.gnu.org>
2018-02-10 19:25 ` Zaak Beekman
2018-02-10 19:35   ` Steve Kargl
2018-02-10 19:59   ` Damian Rouson
2018-02-10 21:07   ` Janne Blomqvist [this message]
2018-02-21 23:31 Dominique d'Humières
2018-02-21 23:39 ` Damian Rouson
  -- strict thread matches above, loose matches on Subject: below --
2018-02-09 16:11 Janne Blomqvist
2018-02-09 23:27 ` Steve Kargl
2018-02-10 19:34 ` Damian Rouson
2018-02-10 21:21   ` Janne Blomqvist
2018-02-21 19:35     ` Janne Blomqvist
2018-02-21 20:19       ` Damian Rouson
2018-02-21 20:56         ` Janne Blomqvist
2018-02-21 20:59           ` Izaak Beekman
2018-02-22  0:36           ` Damian Rouson
2018-02-22  9:46             ` Janne Blomqvist
2018-02-22  9:57               ` Janne Blomqvist

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='CAO9iq9EHev9zWW+iU6W-3hc27taKQ+Np_SER=XTV2gJXOMuxWA@mail.gmail.com' \
    --to=blomqvist.janne@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=zbeekman@gmail.com \
    /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).