[Bug fortran/29616] Run-time check using nullified pointers and deallocated variables

2018-02-20 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29616 --- Comment #5 from Dominique d'Humieres --- Compiling the test in comment 0 with -fcheck=all gives At line 5 of file pr29616.f90 Fortran runtime error: Pointer actual argument 'r' is not associated since at least 4.8.

[Bug fortran/29616] Run-time check using nullified pointers and deallocated variables

2009-06-30 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2009-06-30 15:21 --- PR 39230 is connected to item (c) in comment #3. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29616

[Bug fortran/29616] Run-time check using nullified pointers and deallocated variables

2009-06-29 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2009-06-29 21:00 --- PR 40580 added an argument checking for pointer/proc-pointer/allocatable, i.e. the example call foo(r) of comment 0 is now detected via -fcheck=pointer. TODO: a) call sub( uninit_alloc_returning_function() ) does

[Bug fortran/29616] Run-time check using nullified pointers and deallocated variables

2007-03-22 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-03-22 22:30 --- Besides pointers, the same is also true for deallocated variables, only that the unknown state does not exist. (Idea taken from 31318) I think there are essentially two problems possible with pointers: (a)

[Bug fortran/29616] Run-time check using nullified pointers and deallocated variables

2007-03-22 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-03-22 22:32 --- *** Bug 31318 has been marked as a duplicate of this bug. *** -- burnus at gcc dot gnu dot org changed: What|Removed |Added