From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "José Rui Faustino de Sousa" <jrfsousa@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran v2] PR fortran/84006, PR fortran/100027 - ICE on storage_size with polymorphic argument
Date: Sat, 17 Apr 2021 15:36:35 +0100 [thread overview]
Message-ID: <CAGkQGiLh7KdBVNKbzo94fE2VSxxo7JHwHc5-k=XCy1C2ChhW5A@mail.gmail.com> (raw)
In-Reply-To: <b15e3a2c-c165-6c79-4cae-4ced11bebcb4@gmail.com>
Hi Jose,
Please take a look at my reply on the PR, which points to PR98534.
Regards
Paul
On Fri, 16 Apr 2021 at 20:47, José Rui Faustino de Sousa via Fortran <
fortran@gcc.gnu.org> wrote:
> Hi All!
>
> Proposed patch to:
> PR84006 - [8/9/10/11 Regression] ICE in storage_size() with CLASS entity
> PR100027 - ICE on storage_size with polymorphic argument
>
> Patch tested only on x86_64-pc-linux-gnu.
>
> Add branch to if clause to handle polymorphic objects, not sure if I got
> all possible variations...
>
> Now with a new and extended test.
>
> Thank you very much.
>
> Best regards,
> José Rui
>
> Fortran: Fix ICE using storage_size intrinsic [PR84006, PR100027]
>
> gcc/fortran/ChangeLog:
>
> PR fortran/84006
> PR fortran/100027
> * trans-intrinsic.c (gfc_conv_intrinsic_storage_size): add if
> clause branch to handle polymorphic objects.
>
> gcc/testsuite/ChangeLog:
>
> PR fortran/84006
> * gfortran.dg/PR84006.f90: New test.
>
> PR fortran/100027
> * gfortran.dg/PR100027.f90: New test.
>
--
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein
prev parent reply other threads:[~2021-04-17 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 18:38 José Rui Faustino de Sousa
2021-04-17 14:36 ` Paul Richard Thomas [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='CAGkQGiLh7KdBVNKbzo94fE2VSxxo7JHwHc5-k=XCy1C2ChhW5A@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jrfsousa@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).