From: Jerry DeLisle <jvdelisle@charter.net>
To: Andre Vehreschild <vehre@gmx.de>,
GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
GCC-Fortran-ML <fortran@gcc.gnu.org>
Subject: Re: [Fortran, PATCH, coarray, v1] Extend caf_*_by_ref () API by a type specifier
Date: Sun, 18 Feb 2018 16:53:00 -0000 [thread overview]
Message-ID: <f893625c-7ce2-8d63-b003-9e212456cef2@charter.net> (raw)
In-Reply-To: <20180218163900.095f4a86@vepi2>
On 02/18/2018 07:39 AM, Andre Vehreschild wrote:
> Hi all,
>
> attached patch fixes an issue with the coarray API. When a component of a
> derived type coarray was referenced using a caf_*_by_ref () function and that
> component was not an array with a descriptor, then the type of the component was
> not known. Which additionally meant, that type conversion was not applied as
> required. This patch fixes that issue by adding type specifiers to the three
> caf_*_by_ref-calls and implements the functionality for libcaf_single. This is
> harmless because other coarray libraries that do not expect this argument just
> ignore it.
> Additionally does this patch also provide the first working version of
> caf_sendget_by_ref in libcaf_single, which previously only lead to a stack
> corruption and was not usable since the array descriptor rework (nice job, btw).
>
> I would like to have this patch in trunk knowing that I am somewhat late, but
> it would be quite necessary, because as it is now, the coarray feature for
> derived types is hardly usable. Furthermore do some people name this a
> regression, because the caf_*_by_ref are also used when the lhs of a
> caf_get_by_ref() is allocatable which now does not work as expected anymore but
> before gcc-6 using caf_get() (w/o reallocation) did.
>
> Bootstrapped and regtested ok on x86_64-linux/f27. Ok for trunk?
>
> - Andre
>
This is OK from the Fortranners perspective. Should touch base with
release manager. It looks harmless though it changes coarray API, which
is hidden behind -fcoarray=
Regards,
Jerry
next prev parent reply other threads:[~2018-02-18 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 15:39 Andre Vehreschild
2018-02-18 16:53 ` Jerry DeLisle [this message]
2018-02-18 17:07 ` Andre Vehreschild
2018-02-18 17:33 ` Andre Vehreschild
2018-02-19 17:32 ` Andre Vehreschild
2018-02-20 18:24 ` Damian Rouson
2018-04-08 17:23 ` 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=f893625c-7ce2-8d63-b003-9e212456cef2@charter.net \
--to=jvdelisle@charter.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=vehre@gmx.de \
/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).