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/38319] New: Memory leaks in allocatable component expressions Date: Sat, 29 Nov 2008 21:55:00 -0000 [thread overview] Message-ID: <bug-38319-10374@http.gcc.gnu.org/bugzilla/> (raw) The following testsuite programs with allocatable components exhibit memory leaks at runtime: alloc_comp_assign_2.f90 FOR_ALL problem(lines 27, 28 and 47) alloc_comp_assign_4.f90 nested constructors(line 56) alloc_comp_basics_2.f90 repeated ALLOCATE (lines 29, 30 and 35) alloc_comp_basics_5.f90 repeated ALLOCATE (lines 29, 30 and 35) alloc_comp_constructor_2.f90 nested constructors(line 23) alloc_comp_initializer_1.f90 nested constructors(line 43) Clearly, the investigation should go in the order: nested constructors => repeated ALLOCATE => FORALL Paul -- Summary: Memory leaks in allocatable component expressions Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: fortran AssignedTo: pault at gcc dot gnu dot org ReportedBy: pault at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38319
next reply other threads:[~2008-11-29 21:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-29 21:55 pault at gcc dot gnu dot org [this message] 2008-11-29 21:55 ` [Bug fortran/38319] " pault at gcc dot gnu dot org 2009-07-30 19:07 ` burnus at gcc dot gnu dot org 2010-02-24 20:31 ` pault at gcc dot gnu dot org 2010-02-25 7:38 ` burnus at gcc dot gnu dot org 2010-02-25 12:51 ` paul dot richard dot thomas at gmail dot com 2010-02-25 13:54 ` burnus 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=bug-38319-10374@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: 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).