--- Comment #9 from fxcoudert at gcc dot gnu dot org 2007-08-15 10:41
---
cp2k compiles fine on i686-darwin as of today, and I can't see the memory leak
any more, so I'm closing this.
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Adde
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-07-15 00:31
---
(In reply to comment #7)
> is this still failing ? Yesterday, I ran a valgrinded compilation of CP2K, and
> it showed no errors (didn't check memory leaks). This has been on x86_64
> though.
Apparently, the ICE o
--- Comment #7 from jv244 at cam dot ac dot uk 2007-07-13 07:17 ---
is this still failing ? Yesterday, I ran a valgrinded compilation of CP2K, and
it showed no errors (didn't check memory leaks). This has been on x86_64
though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32310
--- Comment #6 from jvdelisle at gcc dot gnu dot org 2007-06-17 03:14
---
Created an attachment (id=13716)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13716&action=view)
Valgrind leak check on example code
This shows the huge memory leak. 39 Mbytes! on x86-64 (Intel)
--
h
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-06-17 03:03
---
With valgrind, I am detecting a huge memory leak on x86-64. I am reruning and
will post a log shortly. It takes a while to run the example in comment #1,
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32310
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2007-06-13 08:02
---
(In reply to comment #3)
> Are there any equivalences in the the sources for the modules and do they have
> any data statements? Even if they do, I am not sure that I believe that the
> PR29786 patch is involved
--- Comment #3 from pault at gcc dot gnu dot org 2007-06-13 07:27 ---
(In reply to comment #2)
> I can't reduce that any more, it depends on the module files being huge: if
> you
> trim them down to a lower number of symbols, they ICE disapears. And I can't
> reproduced it either on x86
--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-06-12 22:03
---
I can't reduce that any more, it depends on the module files being huge: if you
trim them down to a lower number of symbols, they ICE disapears. And I can't
reproduced it either on x86_64-linux.
--
http://gcc
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-06-12 18:10
---
Created an attachment (id=13692)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13692&action=view)
Testcase and module files that generate the ICE
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32310