public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@net-b.de>
To: gcc patches <gcc-patches@gcc.gnu.org>,
	gfortran <fortran@gcc.gnu.org>,
	 Jerry DeLisle <jvdelisle2@gmail.com>
Subject: Re: [Patch, Fortran] PR55469 - fix I/O memory leaks in case of failure and iostat= being present
Date: Tue, 01 Oct 2013 20:54:00 -0000	[thread overview]
Message-ID: <524B3666.7020107@net-b.de> (raw)
In-Reply-To: <50B7492B.5030702@net-b.de>

I have committed the patch after Janne's approval on IRC  and fresh 
building/regtesting as Rev. 203086. See 
http://gcc.gnu.org/ml/fortran/2012-11/msg00092.html

As suggested by Janne, I will backport it to 4.8 in in a bunch of days.

Tobias

On November 29, 2012 12:38, Tobias Burnus wrote:
> Tobias Burnus wrote:
>> l_push_char allocates memory which is freed with free_line. However, 
>> currently, the memory is not always freed when calling 
>> generate_error. If one aborts, that's fine. However, generate_error 
>> can also set the iostat variable.
>
> Updated version: Corrected PR number - and ensured that if 
> convert_real fails, free_saved is called (cf. additional test case in 
> the PR).
>
> Build and regtested on x86-64-gnu-linux.
> OK for the trunk?
>
> Tobias

      parent reply	other threads:[~2013-10-01 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 16:44 [Patch, Fortran] PR5469 Tobias Burnus
2012-11-29 11:38 ` [Patch, Fortran] PR55469 - fix I/O memory leaks in case of failure and iostat= being present Tobias Burnus
2012-11-29 12:02   ` Janne Blomqvist
2013-10-01 20:54   ` Tobias Burnus [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=524B3666.7020107@net-b.de \
    --to=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle2@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).