From: Andre Vehreschild <vehre@gmx.de>
To: GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
GCC-Fortran-ML <fortran@gcc.gnu.org>
Subject: Re: [Fortran, patch, coarray, v1] Fix a coarray issue and some documentation
Date: Sun, 11 Feb 2018 19:16:00 -0000 [thread overview]
Message-ID: <20180211201648.6cb1e700@vepi2> (raw)
In-Reply-To: <20180211200005.19828130@vepi2>
Er, the revision is 257567. Sorry pressed to quickly.
- Andre
On Sun, 11 Feb 2018 20:00:05 +0100
Andre Vehreschild <vehre@gmx.de> wrote:
> Hi all,
>
> approved on IRC by Kargl. Thanks for the quick review. Committed as r
>
> Regards,
> Andre
>
> On Sun, 11 Feb 2018 18:13:35 +0100
> Andre Vehreschild <vehre@gmx.de> wrote:
>
> > Hi all,
> >
> > attached patch fixes a small coarray issue on ultimate component coarrays.
> > The coarray was registered with the caf-library as if it were an allocatable
> > component in a derived type coarray, which is just wasting resources. An
> > ultimate component coarray has to be treated like a regular coarray. The
> > second chunk of the patch fixes that.
> >
> > The first chunk of the attached patch just fixes some typos and style I
> > found while reading the help text for caf_register(). Those are so small
> > that I did not want to add another patch for this, given that both parts of
> > the patch are somehow related.
> >
> > Bootstrapped and regtested on x86_64-linux-gnu/f27. Ok for trunk?
> >
> > Regards,
> > Andre
>
>
--
Andre Vehreschild * Email: vehre ad gmx dot de
prev parent reply other threads:[~2018-02-11 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 17:13 Andre Vehreschild
2018-02-11 19:00 ` Andre Vehreschild
2018-02-11 19:16 ` Andre Vehreschild [this message]
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=20180211201648.6cb1e700@vepi2 \
--to=vehre@gmx.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).