[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[dominiq at lps dot ens.fr via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

Dominique d'Humieres  changed:

   What|Removed |Added

 Status|ASSIGNED|NEW

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[pault at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

Paul Thomas  changed:

   What|Removed |Added

   Assignee|pault at gcc dot gnu.org   |unassigned at gcc dot 
gnu.org

--- Comment #9 from Paul Thomas  ---
(In reply to Thomas Koenig from comment #8)
> We have an unsigned short in our descriptor that we can use
> for keeping track of what we allocated and where.
> 
> So, we have 16 bits. State we can keep around is:
> 
> Type of descriptor: Allocatable, pointer, passed argument.  2 bits.
> 
> Associated: No, allocated, target.  2 bits.
> 
> Contiguous: 1 bit.
> 
> Anything else we would need?  That would still leave us 11 bit in reserve.

Hi Thomas,

That was the intention of the field in the descriptor. I just never got round
to it.

I have unassigned myself since I have a huge backlog of other issues.

Cheers

Paul

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[tkoenig at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

--- Comment #8 from Thomas Koenig  ---
We have an unsigned short in our descriptor that we can use
for keeping track of what we allocated and where.

So, we have 16 bits. State we can keep around is:

Type of descriptor: Allocatable, pointer, passed argument.  2 bits.

Associated: No, allocated, target.  2 bits.

Contiguous: 1 bit.

Anything else we would need?  That would still leave us 11 bit in reserve.

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[tkoenig at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

Thomas Koenig  changed:

   What|Removed |Added

 CC||longb at cray dot com

--- Comment #7 from Thomas Koenig  ---
*** Bug 68927 has been marked as a duplicate of this bug. ***

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[juergen.reuter at desy dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

--- Comment #6 from Jürgen Reuter  ---
Still present in trunk.

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[pault at gcc dot gnu dot org]

-- 

pault at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |pault at gcc dot gnu dot org
   |dot org |
 Status|SUSPENDED   |ASSIGNED
   Last reconfirmed|2008-03-27 16:50:00 |2009-04-06 10:55:56
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[pault at gcc dot gnu dot org]

--- Comment #5 from pault at gcc dot gnu dot org  2008-11-06 06:23 ---
Hold this one to 4.5 since it needs the array descriptor reform.

Paul


-- 

pault at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |SUSPENDED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[pault at gcc dot gnu dot org]

--- Comment #4 from pault at gcc dot gnu dot org  2008-09-28 19:54 ---
(In reply to comment #3)
> works correctly with e.g. ifort and xlf90, so worth fixing somehow.
> 
Thomas' #2 is correct - see the present discussion on the list.

I think that we have to bite the bullet and change the API.

Paul


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[jv244 at cam dot ac dot uk]

--- Comment #3 from jv244 at cam dot ac dot uk  2008-08-08 21:13 ---
works correctly with e.g. ifort and xlf90, so worth fixing somehow.


-- 

jv244 at cam dot ac dot uk changed:

   What|Removed |Added

  Known to fail||4.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[tkoenig at gcc dot gnu dot org]

--- Comment #2 from tkoenig at gcc dot gnu dot org  2008-04-13 20:58 ---
Ouch.  That one will be hard to fix without keeping
state around in the descriptor.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718

[Bug fortran/35718] deallocating non-allocated pointer target does not fail

[burnus at gcc dot gnu dot org]

--- Comment #1 from burnus at gcc dot gnu dot org  2008-03-27 16:50 ---
Confirmed. gfortran deallocates the static memory as valgrind also complains:

==3839== Invalid free() / delete / delete[]
==3839==at 0x4C2430F: free (in
/usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==3839==by 0x4008F2: MAIN__ (aaa.f90:12)
==3839==by 0x4009BB: main (fmain.c:21)


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Keywords||wrong-code
   Last reconfirmed|-00-00 00:00:00 |2008-03-27 16:50:00
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35718