From: Jerry DeLisle <jvdelisle@charter.net>
To: Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: *ping* [patch, fortran] Fix handling of assumed-size arrays in inline matmul
Date: Sat, 17 Feb 2018 15:27:00 -0000 [thread overview]
Message-ID: <a10beda0-8902-905a-7d06-8bc595e45144@charter.net> (raw)
In-Reply-To: <d3647f5a-da83-f6d7-3a4e-7bf533909b26@netcologne.de>
On 02/17/2018 06:22 AM, Thomas Koenig wrote:
> Am 12.02.2018 um 11:46 schrieb Thomas Koenig:
>> Hello world,
>>
>> the attached patch fixes a regression where a rejects-valid would
>> be issued.
>>
>> OK for the affected branches, trunk and gcc-7?
>
> PING ** (5.D0/7.D0) ?
>
>
Yes, OK
Jerry
prev parent reply other threads:[~2018-02-17 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 10:46 Thomas Koenig
2018-02-17 14:22 ` *ping* " Thomas Koenig
2018-02-17 15:27 ` Jerry DeLisle [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=a10beda0-8902-905a-7d06-8bc595e45144@charter.net \
--to=jvdelisle@charter.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.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).