public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/63473] [4.9/5 Regression] Memory leak with ALLOCATABLE, INTENT(OUT) dummy arguments.
Date: Tue, 16 Dec 2014 14:50:00 -0000 [thread overview]
Message-ID: <bug-63473-4-r9tL7PHo2J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63473-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63473
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-12-16
CC| |janus at gcc dot gnu.org
Version|4.8.2 |4.9.1
Summary|Memory leak with |[4.9/5 Regression] Memory
|ALLOCATABLE, INTENT(OUT) |leak with ALLOCATABLE,
|dummy arguments. |INTENT(OUT) dummy
| |arguments.
Ever confirmed|0 |1
--- Comment #2 from janus at gcc dot gnu.org ---
Confirmed.
> ==13675== 800 bytes in 40 blocks are definitely lost in loss record 2 of 3
> ==13675== at 0x4A069EE: malloc (vg_replace_malloc.c:270)
> ==13675== by 0x400CF0: __testmodule_MOD_create_mytype
> (test_allocarg.f90:15)
> ==13675== by 0x400B74: __testmodule_MOD_allocate_mytype
> (test_allocarg.f90:24)
> ==13675== by 0x400E47: MAIN__ (test_allocarg.f90:40)
> ==13675== by 0x400E94: main (test_allocarg.f90:33)
This one I see with all gfortran versions I tried (4.4.7, 4.6.4, 4.7.4, 4.8.3,
4.9.1, trunk).
> ==13675== 1,360 (960 direct, 400 indirect) bytes in 1 blocks are definitely
> lost in loss record 3 of 3
> ==13675== at 0x4A069EE: malloc (vg_replace_malloc.c:270)
> ==13675== by 0x4009DA: __testmodule_MOD_allocate_mytype
> (test_allocarg.f90:22)
> ==13675== by 0x400E47: MAIN__ (test_allocarg.f90:40)
> ==13675== by 0x400E94: main (test_allocarg.f90:33)
This one only seems to occur with 4.9 and trunk, i.e. it's a regression.
next prev parent reply other threads:[~2014-12-16 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 18:06 [Bug fortran/63473] New: " paul.vandelst at noaa dot gov
2014-12-16 14:50 ` janus at gcc dot gnu.org [this message]
2014-12-16 15:13 ` [Bug fortran/63473] [4.9/5 Regression] " janus at gcc dot gnu.org
2014-12-16 15:26 ` janus at gcc dot gnu.org
2014-12-16 15:34 ` [Bug fortran/63473] " janus at gcc dot gnu.org
2015-08-07 17:26 ` mikael at gcc dot gnu.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-63473-4-r9tL7PHo2J@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).