public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32795] Leaking memory (generated prog) with type constructor & allocatable components Date: Tue, 17 Jul 2007 21:43:00 -0000 [thread overview] Message-ID: <20070717214257.679.qmail@sourceware.org> (raw) In-Reply-To: <bug-32795-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from dfranke at gcc dot gnu dot org 2007-07-17 21:42 ------- After update to r126703, updated example from pr31320, comment #4: type :: a integer, allocatable :: i(:) end type a type(a) :: x, y x = a ((/ 1,2,3 /)) ! y = a (x%i(1:3)) ! ok ! y = a (x%i(1:)) ! ok ! y = a (x%i(:3)) ! ok ! y = a (x%i(:)) ! memory leak ! y = a (x%i) ! memory leak ! y = x ! ok end ==21521== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 1) ==21521== malloc/free: in use at exit: 12 bytes in 1 blocks. ==21521== malloc/free: 12 allocs, 11 frees, 25,539 bytes allocated. ==21521== For counts of detected errors, rerun with: -v ==21521== searching for pointers to 1 not-freed blocks. ==21521== checked 66,236 bytes. ==21521== ==21521== 12 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==21521== at 0x40215CD: malloc (vg_replace_malloc.c:149) ==21521== by 0x80486CC: MAIN__ (in /home/daniel/pr/a.out) ==21521== by 0x8048958: main (fmain.c:22) -- dfranke at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfranke at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32795
next prev parent reply other threads:[~2007-07-17 21:43 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-17 17:57 [Bug fortran/32795] New: " burnus at gcc dot gnu dot org 2007-07-17 21:43 ` dfranke at gcc dot gnu dot org [this message] 2007-07-18 17:12 ` [Bug fortran/32795] [4.3 regression] allocatable components are nullified prematurely dfranke at gcc dot gnu dot org 2007-07-18 17:47 ` [Bug fortran/32795] " dfranke at gcc dot gnu dot org 2007-07-28 20:52 ` pault at gcc dot gnu dot org 2007-08-01 18:39 ` burnus at gcc dot gnu dot org 2008-01-30 22:30 ` burnus at gcc dot gnu dot org 2008-02-07 15:19 ` pault at gcc dot gnu dot org 2008-02-07 17:25 ` dfranke at gcc dot gnu dot org 2008-02-07 19:53 ` dominiq at lps dot ens dot fr 2008-02-07 22:05 ` pault at gcc dot gnu dot org 2008-02-07 22:10 ` dfranke at gcc dot gnu dot org 2008-02-07 22:17 ` burnus at gcc dot gnu dot org 2008-02-07 22:30 ` dfranke at gcc dot gnu dot org 2008-02-19 12:12 ` pault at gcc dot gnu dot org 2008-11-24 6:37 ` pault at gcc dot gnu dot org 2008-11-27 13:26 ` burnus at gcc dot gnu dot org 2008-11-29 20:45 ` pault at gcc dot gnu dot org 2008-11-29 21:58 ` pault at gcc dot gnu dot org
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=20070717214257.679.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: linkBe 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).