From: Harald Anlauf <anlauf@gmx.de>
To: Mikael Morin <morin-mikael@orange.fr>,
fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR fortran/101565 - ICE in gfc_simplify_image_index, at fortran/simplify.c:8234
Date: Tue, 30 Nov 2021 20:47:16 +0100 [thread overview]
Message-ID: <09f13f7a-300a-c48f-c17c-bca2237c0f5e@gmx.de> (raw)
In-Reply-To: <5b1b88fa-62b4-5df7-890c-a0bb70960da4@orange.fr>
Hi Mikael,
Am 30.11.21 um 12:25 schrieb Mikael Morin:
> Hello,
>
> Le 29/11/2021 à 22:31, Harald Anlauf via Fortran a écrit :
>> Dear all,
>>
>> a trivial one: we need to check the type of the SUB argument
>> to the coarray IMAGE_INDEX intrinsic. It has to be an array
>> of type integer.
>>
>> Patch by Steve Kargl.
>>
> I hope at some point he’ll finally come to a working git workflow.
Initially I had to rethink my workflow habits when switching from
svn to git. But after a steep learning curve I wouldn't want to
go back. One day Steve might see it same way.
>> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>>
> Sure.
>
Thanks,
Harald
WARNING: multiple messages have this Message-ID
From: Harald Anlauf <anlauf@gmx.de>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH] PR fortran/101565 - ICE in gfc_simplify_image_index, at fortran/simplify.c:8234
Date: Tue, 30 Nov 2021 20:47:16 +0100 [thread overview]
Message-ID: <09f13f7a-300a-c48f-c17c-bca2237c0f5e@gmx.de> (raw)
Message-ID: <20211130194716.a1O6LR3D7gpkR2ng69Oa8H0Qc-pjpnFpdQk56yYiM30@z> (raw)
In-Reply-To: <5b1b88fa-62b4-5df7-890c-a0bb70960da4@orange.fr>
Hi Mikael,
Am 30.11.21 um 12:25 schrieb Mikael Morin:
> Hello,
>
> Le 29/11/2021 à 22:31, Harald Anlauf via Fortran a écrit :
>> Dear all,
>>
>> a trivial one: we need to check the type of the SUB argument
>> to the coarray IMAGE_INDEX intrinsic. It has to be an array
>> of type integer.
>>
>> Patch by Steve Kargl.
>>
> I hope at some point he’ll finally come to a working git workflow.
Initially I had to rethink my workflow habits when switching from
svn to git. But after a steep learning curve I wouldn't want to
go back. One day Steve might see it same way.
>> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>>
> Sure.
>
Thanks,
Harald
next prev parent reply other threads:[~2021-11-30 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 21:31 Harald Anlauf
2021-11-30 11:25 ` Mikael Morin
2021-11-30 19:47 ` Harald Anlauf [this message]
2021-11-30 19:47 ` Harald Anlauf
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=09f13f7a-300a-c48f-c17c-bca2237c0f5e@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=morin-mikael@orange.fr \
/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).