public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry D <jvdelisle2@gmail.com>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	Jerry D <jvdelisle2@gmail.com>
Subject: Re: [Patch, fortran] PR114535 - [13/14 regression] ICE with elemental finalizer
Date: Mon, 8 Apr 2024 11:23:24 -0700	[thread overview]
Message-ID: <d5756d4d-1c95-4298-954a-45f793b37e98@gmail.com> (raw)
In-Reply-To: <CAGkQGi+QwGbyc44NAsh5TsEVchZYBW5v26H6UDsV9wJCDwDAyQ@mail.gmail.com>

On 4/8/24 2:45 AM, Paul Richard Thomas wrote:
> Hi All,
> 
> This one is blazingly 'obvious'. I haven't had the heart to investigate why somebody thought that it is a good idea to check if unreferenced symbols are finalizable because, I suspect, that 
> 'somebody' was me. Worse, I tried a couple of other fixes before I hit on the 'obvious' one :-(
> 
> The ChangeLog says it all. OK for mainline and then backporting in a couple of weeks?
> 
> Paul
> 
> Fortran: Fix ICE in trans-stmt.cc(gfc_trans_call) [PR114535]
> 
> 2024-04-08  Paul Thomas  <pault@gcc.gnu.org <mailto:pault@gcc.gnu.org>>
> 
> gcc/fortran
> PR fortran/114535
> * resolve.cc (resolve_symbol): Remove last chunk that checked
> for finalization of unreferenced symbols.
> 
> gcc/testsuite/
> PR fortran/114535
> * gfortran.dg/pr114535d.f90: New test.
> * gfortran.dg/pr114535iv.f90: Additional source.
> 

Yes, OK Paul.  Don't feel bad. It wasn't Tabs. LOL

Jerry

      reply	other threads:[~2024-04-08 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08  9:45 Paul Richard Thomas
2024-04-08 18:23 ` Jerry D [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=d5756d4d-1c95-4298-954a-45f793b37e98@gmail.com \
    --to=jvdelisle2@gmail.com \
    --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).