[Bug fortran/32795] allocatable components are nullified prematurely

2008-11-29 Thread pault at gcc dot gnu dot org
--- Comment #18 from pault at gcc dot gnu dot org 2008-11-29 21:56 --- Fixed on trunk and 4.3. Thanks for the report! Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added --

[Bug fortran/32795] allocatable components are nullified prematurely

2008-11-29 Thread pault at gcc dot gnu dot org
--- Comment #17 from pault at gcc dot gnu dot org 2008-11-29 20:43 --- Subject: Bug 32795 Author: pault Date: Sat Nov 29 20:42:22 2008 New Revision: 142284 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142284 Log: 2008-11-24 Paul Thomas <[EMAIL PROTECTED]> PR fortran

[Bug fortran/32795] allocatable components are nullified prematurely

2008-11-27 Thread burnus at gcc dot gnu dot org
--- Comment #16 from burnus at gcc dot gnu dot org 2008-11-27 13:24 --- (Most problems have been fixed, except of the one in comment 0.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32795

[Bug fortran/32795] allocatable components are nullified prematurely

2008-11-23 Thread pault at gcc dot gnu dot org
--- Comment #15 from pault at gcc dot gnu dot org 2008-11-24 06:35 --- Subject: Bug 32795 Author: pault Date: Mon Nov 24 06:34:16 2008 New Revision: 142148 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142148 Log: 2008-11-24 Paul Thomas <[EMAIL PROTECTED]> PR fortran

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-19 Thread pault at gcc dot gnu dot org
--- Comment #14 from pault at gcc dot gnu dot org 2008-02-19 12:12 --- (In reply to comment #12) It is essential to fix the memory leaks - that after all is the purpose behind allocatable components. I´ll see if I can understand what is happening. Cheers Paul -- http://gcc.gnu.o

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread dfranke at gcc dot gnu dot org
--- Comment #13 from dfranke at gcc dot gnu dot org 2008-02-07 22:30 --- > As valgrind --leak-check=full shows, the generated program still > leaks memory Forgot to check this one :( Interestingly, the error seems to be with forall only. The equivalent DO-loop does not leak: type

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread burnus at gcc dot gnu dot org
--- Comment #12 from burnus at gcc dot gnu dot org 2008-02-07 22:17 --- > This is regtesting but all the allocatable component tests are OK. > Could somebody check the memory leakage for me, please? The test of comment 2 > is now OK in that it prints the right numbers. Thanks for the w

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread dfranke at gcc dot gnu dot org
--- Comment #11 from dfranke at gcc dot gnu dot org 2008-02-07 22:10 --- > You mean that one-liner did it I did not regtest, but yes, the testcases from this PR are fixed by the patch attached in comment #7 :) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32795

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread pault at gcc dot gnu dot org
--- Comment #10 from pault at gcc dot gnu dot org 2008-02-07 22:04 --- (In reply to comment #9) > Regtested without regression on ppc/intel-darwin9, 32 and 64 bit modes. > > Thanks for the patch. > Dominique and Daniel, You mean that one-liner did it That represents a seriously

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread dominiq at lps dot ens dot fr
--- Comment #9 from dominiq at lps dot ens dot fr 2008-02-07 19:52 --- Regtested without regression on ppc/intel-darwin9, 32 and 64 bit modes. Thanks for the patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32795

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread dfranke at gcc dot gnu dot org
--- Comment #8 from dfranke at gcc dot gnu dot org 2008-02-07 17:24 --- > Could somebody check the memory leakage for me, please? type :: a integer, allocatable :: i(:) end type a type(a) :: x, y x = a ((/ 1,2,3 /)) ! y = a (x%i(1:3)) ! ok ! y = a (x%i(1:))! o

[Bug fortran/32795] allocatable components are nullified prematurely

2008-02-07 Thread pault at gcc dot gnu dot org
--- Comment #7 from pault at gcc dot gnu dot org 2008-02-07 15:19 --- Created an attachment (id=15116) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15116&action=view) A tentative patch for the PR This is regtesting but all the allocatable component tests are OK. Could somebody c

[Bug fortran/32795] allocatable components are nullified prematurely

2008-01-30 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2008-01-30 22:14 --- Paul's patch with and added if condition (see below) nicely compiles all examples + regtests; however, the example of comment 2 gives a wrong result ("< >" instead of "< 1 2 3 >") [this is independent of the patch]. F

[Bug fortran/32795] allocatable components are nullified prematurely

2007-08-01 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-08-01 18:39 --- > Could somebody test the patch below, please? Build (/= bootstrapped) and check-gfortran'ed (-m64) on x86-64-Linux. I get an ICE (segmentation fault) for gfortran.dg/derived_comp_array_ref_1.f90: ==26501== Invalid r

[Bug fortran/32795] allocatable components are nullified prematurely

2007-07-28 Thread pault at gcc dot gnu dot org
--- Comment #4 from pault at gcc dot gnu dot org 2007-07-28 20:52 --- (In reply to comment #3) Could somebody test the patch below, please? Paul Index: gcc/fortran/trans-stmt.c === *** gcc/fortran/trans-stmt.c(revisio

[Bug fortran/32795] allocatable components are nullified prematurely

2007-07-18 Thread dfranke at gcc dot gnu dot org
--- Comment #3 from dfranke at gcc dot gnu dot org 2007-07-18 17:47 --- Not a regression. The same happenes without the patch for PR31320, as well as with gfortran-4.2. -- dfranke at gcc dot gnu dot org changed: What|Removed |Added --