This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/53521] [4.5/4.6/4.7/4.8 Regression] Zero-byte "memory leak" with zero-sized array constructor (valgrind warning)
- From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 30 May 2012 12:31:18 +0000
- Subject: [Bug fortran/53521] [4.5/4.6/4.7/4.8 Regression] Zero-byte "memory leak" with zero-sized array constructor (valgrind warning)
- Auto-submitted: auto-generated
- References: <bug-53521-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53521
--- Comment #3 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2012-05-30 12:31:18 UTC ---
(In reply to comment #2)
> Well, I think this is a valgrind issue and not a real "leak". Whether you
> want to "optimize" code for the non-NULL case by omitting the NULL check is
> another question of course. It's definitely not wrong-code IMHO.
No, definitely a real bug... not a valgrind issue. If you put a loop around
'CALL T2' the process memory usage is a >1Gb in a few seconds. This is a real
issue which causes our simulation code to crash after 24h of running.