From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Zaak Beekman <zbeekman@gmail.com>
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH] Character length cleanup for Coarray Fortran library
Date: Sat, 10 Feb 2018 19:35:00 -0000 [thread overview]
Message-ID: <20180210193549.GA17325@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAAbnBwYPbZVgmgOPTYOYv4n4iYYidUz0f+1qSDAazT4Zv6VnMQ@mail.gmail.com>
On Sat, Feb 10, 2018 at 07:25:39PM +0000, Zaak Beekman wrote:
>
> 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?
Zaak,
AFAIK, yes, the change will only be made in the 8.0.
We try very to maintain backwards compatibility with older
versions of gfortran, which means we seldomly break the ABI.
However, for 8.0 the introduction of user defined type IO
required a change to the ABI, so we (well mostly Janne and
Thomas) are trying to get other ABR breaking changes into
trunk.
Janne, can you provide Zaak where you think he may need
to check OC's ABI against your change?
--
Steve
next prev parent reply other threads:[~2018-02-10 19:35 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 [this message]
2018-02-10 19:59 ` Damian Rouson
2018-02-10 21:07 ` Janne Blomqvist
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=20180210193549.GA17325@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).