public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29101] Memory leak in gfortran
Date: Mon, 18 Sep 2006 19:29:00 -0000	[thread overview]
Message-ID: <20060918192930.26500.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29101-6552@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pault at gcc dot gnu dot org  2006-09-18 19:29 -------
Thanks Steven, it was just too obvious, wasn't it?

Index: gcc/fortran/trans-stmt.c
===================================================================
--- gcc/fortran/trans-stmt.c    (revision 117030)
+++ gcc/fortran/trans-stmt.c    (working copy)
@@ -1475,6 +1475,8 @@
   if (n != 0)
     gfc_free (labels);

+  gfc_add_block_to_block (&block, &se.post);
+
   return gfc_finish_block (&block);

now gives


    pstr.6 = (char[1:D.960] *) _gfortran_internal_malloc (D.960);
    tolower (pstr.6, D.960, D.958, D.959);
    goto _gfortran_select_string ((void *) &jumptable.5, 2, &L.5, pstr.6,
D.960);
    L.4:;
    *value = 1;
    goto L.5;
    L.3:;
    __result_validate_value = 0;
    goto L.5;
    L.5:;
    _gfortran_internal_free ((void *) pstr.6);


-- 

pault at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stevenb dot gcc at gmail dot
                   |                            |com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29101


  parent reply	other threads:[~2006-09-18 19:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 19:59 [Bug libfortran/29101] New: memory leak in libgfortran franke dot daniel at gmail dot com
2006-09-16  1:29 ` [Bug libfortran/29101] " jvdelisle at gcc dot gnu dot org
2006-09-17 20:14 ` [Bug fortran/29101] Memory leak in gfortran jvdelisle at gcc dot gnu dot org
2006-09-18  6:53 ` pault at gcc dot gnu dot org
2006-09-18  7:50 ` pault at gcc dot gnu dot org
2006-09-18 17:15 ` patchapp at dberlin dot org
2006-09-18 19:29 ` pault at gcc dot gnu dot org [this message]
2006-09-18 20:20 ` pault at gcc dot gnu dot org
2006-09-18 22:24 ` pault at gcc dot gnu dot org
2006-09-18 22:35 ` steven at gcc dot gnu dot org
2006-09-19 11:05 ` pault at gcc dot gnu dot org
2006-09-19 11:25 ` pault at gcc dot gnu dot org
2006-09-19 11:26 ` pault at gcc dot gnu dot org
2006-09-19 11:56 ` paulthomas2 at wanadoo dot fr

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=20060918192930.26500.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).