From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: Fortran List <fortran@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR65677 - Incomplete assignment on deferred-length character variable
Date: Sun, 23 Sep 2018 16:09:00 -0000 [thread overview]
Message-ID: <CAO9iq9GJDC7GY3PFS0=cB7mHt7h9-FCDpgW4PZsNnZg7v6GzuA@mail.gmail.com> (raw)
In-Reply-To: <CAGkQGiKj1XB7=iy0MuTgNKOgKjfmbd2usWGQTd5UqVVJsjO65g@mail.gmail.com>
On Sun, Sep 23, 2018 at 2:57 PM Paul Richard Thomas <
paul.richard.thomas@gmail.com> wrote:
> This is yet another deferred character length problem that this time
> is caused by a dependency in assignment between lhs and rhs
> string_lengths. The comment in the testcase explains all.
>
> Bootstraps and regtests on FC21/x86_64 - OK for trunk and 8-branch?
>
Ok, thanks.
--
Janne Blomqvist
next prev parent reply other threads:[~2018-09-23 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 11:57 Paul Richard Thomas
2018-09-23 16:09 ` Janne Blomqvist [this message]
2018-09-30 17:16 Dominique d'Humières
2018-10-01 7:55 ` Paul Richard Thomas
2018-10-01 10:19 ` Paul Richard Thomas
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='CAO9iq9GJDC7GY3PFS0=cB7mHt7h9-FCDpgW4PZsNnZg7v6GzuA@mail.gmail.com' \
--to=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@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).