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

2020-12-11 Thread 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

2020-12-10 Thread 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 ---

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

2020-06-14 Thread 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, pass

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

2020-06-14 Thread 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 fro

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

2019-01-22 Thread 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

2009-04-06 Thread 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

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

2008-11-05 Thread 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 --

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

2008-09-28 Thread 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

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

2008-08-08 Thread 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 -

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

2008-04-13 Thread 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

2008-03-27 Thread 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) ==38