public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry D <jvdelisle2@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>,
	sgk@troutmask.apl.washington.edu, fortran@gcc.gnu.org,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix fortran/PR114024
Date: Wed, 21 Feb 2024 12:31:34 -0800	[thread overview]
Message-ID: <12fa7775-918c-4132-b632-65f9c7c4084c@gmail.com> (raw)
In-Reply-To: <3444d912-2e79-4e16-a425-79810d161ebb@gmx.de>

On 2/21/24 12:28 PM, Harald Anlauf wrote:
> On 2/21/24 20:41, Jerry D wrote:
>> On 2/21/24 10:30 AM, Steve Kargl wrote:
>>> I have attached a patch to PR114024, see
>>>
>>> https://gcc.gnu.org/pipermail/gcc-bugs/2024-February/854651.html
>>>
>>> The patch contains a new testcase and passes regression
>>> testing on x86_64-*-freebsd.  Could someone castr an eye
>>> over the patch and commit it?
>>>
>>
>> Hi Steve,
>>
>> I looked it over and looks reasonable.  I will try to apply it next few
>> days and test here. If OK, I will commit.
>>
>> Jerry
>>
> 
> Actually the patch has two issues:
> 
> - a minor one: a new front-end memleak which can be avoided by
>    using either gfc_replace_expr (see its other uses)
>    Hint: try valgrind on f951

Yes, I am learning to do that.

> 
> - it still fails on the following code, because the traversal
>    of the refs is incomplete / wrong:
> 
> program foo
>     implicit none
>     complex               :: cmp(3)
>     real, pointer         :: pp(:)
>     class(*), allocatable :: uu(:)
>     type t
>        real :: re
>        real :: im
>     end type t
>     type u
>        type(t) :: tt(3)
>     end type u
>     type(u) :: cc
> 
>     cmp = (3.45,6.78)
>     cc% tt% re = cmp% re
>     cc% tt% im = cmp% im
>     allocate (pp, source = cc% tt% im)       ! ICE
>     print *, pp
>     allocate (uu, source = cc% tt% im)       ! ICE
> end
> 
> This still crashes for me for the indicated cases.
> 
> Harald
> 

Good catch.  I will hold off until that is figured out.

Jerry

  reply	other threads:[~2024-02-21 20:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 18:30 Steve Kargl
2024-02-21 19:41 ` Jerry D
2024-02-21 20:28   ` Harald Anlauf
2024-02-21 20:31     ` Jerry D [this message]
2024-02-21 21:00     ` Steve Kargl
2024-02-21 21:20       ` Harald Anlauf
2024-02-21 21:42         ` Steve Kargl
2024-02-22  0:52           ` Steve Kargl
2024-02-22 20:22             ` Harald Anlauf
2024-02-22 21:01               ` Steve Kargl
2024-02-22 21:32                 ` Harald Anlauf
2024-02-23 21:15                   ` [PATCH, v2] " Harald Anlauf
2024-02-23 21:32                     ` rep.dot.nop
2024-02-23 21:34                     ` Steve Kargl

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=12fa7775-918c-4132-b632-65f9c7c4084c@gmail.com \
    --to=jvdelisle2@gmail.com \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).