public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53521] [4.5/4.6/4.7 Regression] Memory leak with zero-sized array constructor
Date: Fri, 01 Jun 2012 20:41:00 -0000	[thread overview]
Message-ID: <bug-53521-4-pR6Y8NxQuR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53521-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-06-01 20:40:45 UTC ---
Author: burnus
Date: Fri Jun  1 20:40:36 2012
New Revision: 188125

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=188125
Log:
2012-06-01  Tobias Burnus  <burnus@net-b.de>

        PR fortran/53521
        * trans.c (gfc_deallocate_scalar_with_status): Properly
        handle the case size == 0.


Modified:
    branches/gcc-4_5-branch/gcc/fortran/ChangeLog
    branches/gcc-4_5-branch/gcc/fortran/trans.c


  parent reply	other threads:[~2012-06-01 20:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 19:27 [Bug fortran/53521] New: Memory leak with zero sized " Joost.VandeVondele at mat dot ethz.ch
2012-05-30  8:38 ` [Bug fortran/53521] [4.3/4.4/4.5/4.6/4.7/4.8 Regression] Zero-byte memory leak with zero-sized " burnus at gcc dot gnu.org
2012-05-30  9:56 ` [Bug fortran/53521] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-05-30 12:32 ` [Bug fortran/53521] [4.5/4.6/4.7/4.8 Regression] Zero-byte "memory leak" with zero-sized array constructor (valgrind warning) Joost.VandeVondele at mat dot ethz.ch
2012-05-30 12:49 ` rguenth at gcc dot gnu.org
2012-05-30 14:37 ` jakub at gcc dot gnu.org
2012-05-30 14:38 ` Joost.VandeVondele at mat dot ethz.ch
2012-05-31  8:16 ` [Bug fortran/53521] [4.5/4.6/4.7/4.8 Regression] Memory leak with zero-sized array constructor burnus at gcc dot gnu.org
2012-05-31  8:44 ` jakub at gcc dot gnu.org
2012-05-31 14:29 ` burnus at gcc dot gnu.org
2012-06-01  7:43 ` [Bug fortran/53521] [4.5/4.6/4.7 " Joost.VandeVondele at mat dot ethz.ch
2012-06-01 15:08 ` burnus at gcc dot gnu.org
2012-06-01 20:07 ` burnus at gcc dot gnu.org
2012-06-01 20:41 ` burnus at gcc dot gnu.org [this message]
2012-06-01 21:08 ` [Bug fortran/53521] [4.5/4.6/4.7/4.8 " burnus at gcc dot gnu.org
2013-02-27 12:45 ` dominiq at lps dot ens.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=bug-53521-4-pR6Y8NxQuR@http.gcc.gnu.org/bugzilla/ \
    --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).