public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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] PR93678 - [11/12/13/14 Regression] ICE with TRANSFER and typebound procedures
Date: Wed, 24 Apr 2024 21:26:19 +0200	[thread overview]
Message-ID: <eb36bae6-e103-483c-9ec1-facfff549f4c@gmx.de> (raw)
In-Reply-To: <CAGkQGiJeEFKjGC-9CeDusGSkYj3VQZBR0nY9LTSPZfVijn9uwA@mail.gmail.com>

Hi Paul,

On 4/24/24 18:26, Paul Richard Thomas wrote:
> Hi there,
>
> This regression turned out to be low hanging fruit, although it has taken
> four years to reach it :-(
>
> The ChangeLog says it all. OK for mainline and backporting after a suitable
> delay?

yes to both.

Thanks for "picking" this fruit!

Harald

> Paul
>
> Fortran: Fix ICE in gfc_trans_create_temp_array from bad type [PR93678]
>
> 2024-04-24  Paul Thomas  <pault@gcc.gnu.org>
>
> gcc/fortran
> PR fortran/93678
> * trans-expr.cc (gfc_conv_procedure_call): Use the interface,
> where possible, to obtain the type of character procedure
> pointers of class entities.
>
> gcc/testsuite/
> PR fortran/93678
> * gfortran.dg/pr93678.f90: New test.
>


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, fortran] PR93678 - [11/12/13/14 Regression] ICE with TRANSFER and typebound procedures
Date: Wed, 24 Apr 2024 21:26:19 +0200	[thread overview]
Message-ID: <eb36bae6-e103-483c-9ec1-facfff549f4c@gmx.de> (raw)
Message-ID: <20240424192619.EXot3xXJPVvrGSGt7rX84CC6-zbsiOfGhxoEFzZimd8@z> (raw)
In-Reply-To: <CAGkQGiJeEFKjGC-9CeDusGSkYj3VQZBR0nY9LTSPZfVijn9uwA@mail.gmail.com>

Hi Paul,

On 4/24/24 18:26, Paul Richard Thomas wrote:
> Hi there,
> 
> This regression turned out to be low hanging fruit, although it has taken
> four years to reach it :-(
> 
> The ChangeLog says it all. OK for mainline and backporting after a suitable
> delay?

yes to both.

Thanks for "picking" this fruit!

Harald

> Paul
> 
> Fortran: Fix ICE in gfc_trans_create_temp_array from bad type [PR93678]
> 
> 2024-04-24  Paul Thomas  <pault@gcc.gnu.org>
> 
> gcc/fortran
> PR fortran/93678
> * trans-expr.cc (gfc_conv_procedure_call): Use the interface,
> where possible, to obtain the type of character procedure
> pointers of class entities.
> 
> gcc/testsuite/
> PR fortran/93678
> * gfortran.dg/pr93678.f90: New test.
> 



  reply	other threads:[~2024-04-24 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 16:26 Paul Richard Thomas
2024-04-24 19:26 ` Harald Anlauf [this message]
2024-04-24 19:26   ` 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=eb36bae6-e103-483c-9ec1-facfff549f4c@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).