https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
--- Comment #7 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri Sep 25 22:59:15 2015
New Revision: 228158
URL: https://gcc.gnu.org/viewcvs?rev=228158&root=gcc&view=rev
Log:
2015-09-25 Steven G. Kargl
PR fortran/67614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
--- Comment #6 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri Sep 25 22:30:26 2015
New Revision: 228156
URL: https://gcc.gnu.org/viewcvs?rev=228156&root=gcc&view=rev
Log:
2015-09-25 Steven G. Kargl
PR fortran/67614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
--- Comment #5 from Gerhard Steinmetz
---
For comparison, a logical if (assumes scalar-logical-expr
instead of scalar-numeric-expr in arithmetic if) "avoids"
an ICE. Analogous examples :
$ cat y1.f90
program p
logical, allocatable :: z
i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
--- Comment #4 from Gerhard Steinmetz
---
In general, a future extension to check pointer status
looks promising (at compile time and runtime).
With a tiny and simple source the problem is clear and
obvious, but for large and complex codes ofte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67614
--- Comment #1 from Gerhard Steinmetz
---
$ cat z4.f90
program p
integer, pointer :: z => null()
if ( z ) 1, 2, 3
1 stop 1
2 stop 2
3 stop 3
end
$ gfortran -g -O0 -Wall -fcheck=all -fno-frontend-optimize z4.f90
$ a.out
Program receive
