From: Harald Anlauf <anlauf@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR103366 - [9/10/11/12 Regression] ICE in gfc_conv_gfc_desc_to_cfi_desc, at fortran/trans-expr.c:5647
Date: Fri, 7 Jan 2022 22:05:38 +0100 [thread overview]
Message-ID: <155976dc-2516-6409-4bf3-746bdeb27eb9@gmx.de> (raw)
In-Reply-To: <CAGkQGiLmYgpdcpU7GeF3Nh7=hu-uFhOBrJbAMzZhenXSgGOE9w@mail.gmail.com>
Hi Paul,
Am 07.01.22 um 14:42 schrieb Paul Richard Thomas via Fortran:
> I doubt that this is a regression on 9-11 branches since the testcase
> compiles correctly on each of my copies of these branches. IMHO it is
> rather more likely to have been caused by
> 64f9623765da3306b0ab6a47997dc5d62c2ea261, which introduced this new form of
> gfc_conv_gfc_desc_to_cfi_desc.
>
> The patch is self-explanatory. OK for mainline?
I do not have a copy of F2017; but I can find your comment in the F2018
document.
OK with this change.
Thanks for the patch!
Harald
> Paul
>
> Fortran: Match unlimited polymorphic argument to assumed type [PR103366].
>
> 2022-01-07 Paul Thomas <pault@gcc.gnu.org>
>
> gcc/fortran
> PR fortran/103366
> * trans-expr.c (gfc_conv_gfc_desc_to_cfi_desc): Allow unlimited
> polymorphic actual argument passed to assumed type formal.
>
> gcc/testsuite/
> PR fortran/103366
> * gfortran.dg/pr103366.f90: New test.
prev parent reply other threads:[~2022-01-07 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 13:42 Paul Richard Thomas
2022-01-07 21:05 ` Harald Anlauf [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=155976dc-2516-6409-4bf3-746bdeb27eb9@gmx.de \
--to=anlauf@gmx.de \
--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).