[Bug fortran/35892] gfortran lost memory blocks

2008-04-26 Thread jvdelisle at gcc dot gnu dot org
--- Comment #25 from jvdelisle at gcc dot gnu dot org 2008-04-27 01:08 --- Memory leaks are now gone. Not sure why, but no complaints here -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added --

[Bug fortran/35892] gfortran lost memory blocks

2008-04-26 Thread george at gcc dot gnu dot org
--- Comment #24 from george at gcc dot gnu dot org 2008-04-26 10:18 --- ICE/segfault on test case eliminated by rev. 134696. Memory leaks unrelated to original patch still unresolved. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35892

[Bug fortran/35892] gfortran lost memory blocks

2008-04-26 Thread george at gcc dot gnu dot org
--- Comment #23 from george at gcc dot gnu dot org 2008-04-26 09:46 --- Subject: Bug 35892 Author: george Date: Sat Apr 26 09:46:01 2008 New Revision: 134696 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=134696 Log: 2008-04-26 George Helffrich <[EMAIL PROTECTED]> PR f

[Bug fortran/35892] gfortran lost memory blocks

2008-04-25 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #22 from KnowlesPJ at Cardiff dot ac dot uk 2008-04-25 08:10 --- Yes, this was the silver bullet. With Using built-in specs. Target: i386-apple-darwin9.2.2 Configured with: ../configure --prefix=/opt/gcc Thread model: posix gcc version 4.4.0 20080424 (experimental) (GCC)

[Bug fortran/35892] gfortran lost memory blocks

2008-04-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #21 from jvdelisle at gcc dot gnu dot org 2008-04-24 19:10 --- Reply to comment #18. I have not had time to dig further on these memory issues. I think after George has a revamped patch in, I will explore some more on this. We are probably just not freeing some memory aft

[Bug fortran/35892] gfortran lost memory blocks

2008-04-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #20 from jvdelisle at gcc dot gnu dot org 2008-04-24 19:05 --- The part that was causing the crash has been reverted. Can you try with current latest trunk version 4.4.0 and see if it really is the silver bullet? and report back here. -- http://gcc.gnu.org/bugzilla/sh

[Bug fortran/35892] gfortran lost memory blocks

2008-04-24 Thread KnowlesPJ at Cardiff dot ac dot uk
--- Comment #19 from KnowlesPJ at Cardiff dot ac dot uk 2008-04-24 09:34 --- As the originator of this report, I just wanted to add a context comment in case it is helpful. This construction (common declared both in the module and in subroutines (contained or external)) is horrible, but

[Bug fortran/35892] gfortran lost memory blocks

2008-04-24 Thread george at gcc dot gnu dot org
--- Comment #18 from george at gcc dot gnu dot org 2008-04-24 08:29 --- I've investigated the PR code further. The relevant parts of the code are structured like so: module mod integer aa, bb common /oof/ aa,bb contains subroutine sub i = max(0,aa-1) print *, i, aa, bb end

[Bug fortran/35892] gfortran lost memory blocks

2008-04-19 Thread jvdelisle at gcc dot gnu dot org
--- Comment #17 from jvdelisle at gcc dot gnu dot org 2008-04-19 21:12 --- I am reopening this PR. In my further attempts to reduce the test case here to help with the "apparent" problem with PR35154 I have discovered two things: 1. The test case can only be reduced slightly before th