From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Mikael Morin <mikael.morin@sfr.fr>
Cc: Andre Vehreschild <vehre@gmx.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Damian Rouson <damian@sourceryinstitute.org>
Subject: Re: [Patch, fortran] PR66079 - [6 Regression] memory leak with source allocation in internal subprogram
Date: Thu, 11 Jun 2015 16:00:00 -0000 [thread overview]
Message-ID: <CAGkQGiKT2tHKF7_wHUqG4q8XkL=nogeMN5Uc1f9by_e8Wg61mQ@mail.gmail.com> (raw)
In-Reply-To: <55635CD8.5070005@sfr.fr>
Dear Andre and Mikael,
Thanks for the reviews and the discussion about the name of the
temporary. I went for "source" in the end. The "expr3" was merely
meant to align with the expression....
Following Andre's suggestion, I left his additions to another time;
especially since the patch was heading towards bit-rot because I have
been so long in getting back to it.
Committed to trunk as revision 224383.
Cheers
Paul
On 25 May 2015 at 19:33, Mikael Morin <mikael.morin@sfr.fr> wrote:
> Le 25/05/2015 09:30, Paul Richard Thomas a écrit :
>> Dear All,
>>
>> Lets see if I can get it right this time :-)
>>
>> Note that I have changed the name of the temporary variable in
>> trans_allocate from 'atmp' to 'expr3' so that it is not confused with
>> array temporaries.
> I agree with Andre willing to use a more explicit name ("source"), and I
> suggest pushing it yet further; something like "alloc_source_tmp".
> We should never have named things "expr3" all over the place, but
> that's another matter.
>
>> Bootstrapped and regtested on a current trunk - OK for trunk?
>>
> Yes, looks good. Thanks.
>
> Mikael
--
Outside of a dog, a book is a man's best friend. Inside of a dog it's
too dark to read.
Groucho Marx
next prev parent reply other threads:[~2015-06-11 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 17:53 Paul Richard Thomas
2015-05-23 21:30 ` Andre Vehreschild
2015-05-23 21:35 ` Paul Richard Thomas
2015-05-24 18:55 ` Andre Vehreschild
2015-05-24 11:25 ` Paul Richard Thomas
2015-05-25 10:25 ` Paul Richard Thomas
2015-05-25 11:52 ` Andre Vehreschild
2015-05-25 18:09 ` Mikael Morin
2015-05-27 8:38 ` Paul Richard Thomas
2015-05-27 14:16 ` Andre Vehreschild
2015-05-27 16:42 ` Mikael Morin
2015-05-27 21:28 ` Steve Kargl
2015-05-28 15:22 ` Mikael Morin
2015-05-28 15:24 ` Andre Vehreschild
2015-05-25 18:08 ` Mikael Morin
2015-05-25 18:41 ` Steve Kargl
2015-06-11 16:00 ` Paul Richard Thomas [this message]
2015-10-18 20:04 ` Paul Richard Thomas
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='CAGkQGiKT2tHKF7_wHUqG4q8XkL=nogeMN5Uc1f9by_e8Wg61mQ@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
--cc=vehre@gmx.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).