public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janus Weil <janus@gcc.gnu.org>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
	gfortran <fortran@gcc.gnu.org>,
		gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, F03] PR 80983: memory leak when calling procedure-pointer component with allocatable result
Date: Fri, 16 Jun 2017 10:16:00 -0000	[thread overview]
Message-ID: <CAKwh3qibqH7_UsMf-7fGME+aobtWQzum5hRzS2vzfa2-L8-kew@mail.gmail.com> (raw)
In-Reply-To: <CAKdteOYWe6oND7GjxM6PSK1PjoXM-6YnNiAqQSYPchfuekJmMw@mail.gmail.com>

2017-06-16 11:11 GMT+02:00 Christophe Lyon <christophe.lyon@linaro.org>:
> Hi,
>
> On 15 June 2017 at 23:18, Janus Weil <janus@gcc.gnu.org> wrote:
>> 2017-06-15 15:33 GMT+02:00 Thomas Koenig <tkoenig@netcologne.de>:
>>> Hi Janus,
>>>
>>>> It regtests cleanly on x86_64-linux-gnu. Ok for trunk?
>>>
>>>
>>> OK.
>>>
>>> Thanks for the patch!
>>
>> Thanks, Thomas! Committed as r249227.
>>
>
> There's a problem with the new test. It says:
> gfortran.dg/proc_ptr_comp_51.f90   -O  : dump file does not exist
> UNRESOLVED: gfortran.dg/proc_ptr_comp_51.f90   -O
> scan-tree-dump-times original "__builtin_free" 3
>
> You probably either want to add:
> ! { dg-options "-fdump-tree-original" }
> or to remove:
> ! { dg-final { scan-tree-dump-times "__builtin_free" 3 "original" } }

Thanks for your attention, Christophe. I wanted the first of these two
options, but apparently forgot that line ... :(

Fixed with r249243.

Cheers,
Janus

      reply	other threads:[~2017-06-16 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 12:07 Janus Weil
2017-06-15 13:33 ` Thomas Koenig
2017-06-15 21:18   ` Janus Weil
2017-06-16  9:11     ` Christophe Lyon
2017-06-16 10:16       ` Janus Weil [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=CAKwh3qibqH7_UsMf-7fGME+aobtWQzum5hRzS2vzfa2-L8-kew@mail.gmail.com \
    --to=janus@gcc.gnu.org \
    --cc=christophe.lyon@linaro.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).