[Bug fortran/41586] Allocatable _scalars_ are never auto-deallocated

2009-10-19 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2009-10-19 18:46 --- Mine. Have a patch: http://gcc.gnu.org/ml/fortran/2009-10/msg00171.html -- janus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41586] Allocatable _scalars_ are never auto-deallocated

2009-10-19 Thread janus at gcc dot gnu dot org
--- Comment #5 from janus at gcc dot gnu dot org 2009-10-19 19:21 --- Subject: Bug 41586 Author: janus Date: Mon Oct 19 19:21:18 2009 New Revision: 152988 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=152988 Log: 2009-10-19 Janus Weil ja...@gcc.gnu.org PR

[Bug fortran/41586] Allocatable _scalars_ are never auto-deallocated

2009-10-19 Thread janus at gcc dot gnu dot org
--- Comment #6 from janus at gcc dot gnu dot org 2009-10-19 19:23 --- Fixed with r152988. Closing. -- janus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41586] Allocatable _scalars_ are never auto-deallocated

2009-10-16 Thread janus at gcc dot gnu dot org
--- Comment #3 from janus at gcc dot gnu dot org 2009-10-16 21:04 --- AND ALSO FOR: type t0 end type t0 type(t0), allocatable :: m(:) allocate(t0 :: m(3)) end No, this one actually works (since 'm' is not a scalar): if (m.data != 0B) { __builtin_free ((void *)

[Bug fortran/41586] Allocatable _scalars_ are never auto-deallocated

2009-10-11 Thread tkoenig at gcc dot gnu dot org
--- Comment #2 from tkoenig at gcc dot gnu dot org 2009-10-11 16:44 --- Confirmed. -- tkoenig at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41586] Allocatable _scalars_ are never auto-deallocated

2009-10-05 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2009-10-05 15:17 --- Does not need to be a component or derived type, any scalar leaks: integer , allocatable :: a allocate(a) a = 42 end MAIN__ () { integer(kind=4) * a; { void * restrict D.1366; D.1366 = (void *