[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 janus at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #11 from janus at gcc dot gnu.org 2011-08-17 09:14:24 UTC --- Author: janus Date: Wed Aug 17 09:14:18 2011 New Revision: 177825 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177825 Log: 2011-08-17 Janus Weil PR fortran/

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #10 from janus at gcc dot gnu.org 2011-08-16 09:19:07 UTC --- Here is a patch which rejects the test case with a different error message than comment #6: Index: gcc/fortran/resolve.c ===

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #9 from janus at gcc dot gnu.org 2011-08-15 09:49:44 UTC --- Btw, for a related test case ... subroutine sub common n,z integer z(n) end ... gfortran spits out: integer z(n) 1 Error: Variable 'n' at (1) in this co

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #8 from janus at gcc dot gnu.org 2011-08-15 09:15:36 UTC --- (In reply to comment #4) > Based on chapter 7.1.11, I would say that g95's error message is wrong: z does > not have to have constant length. Well, to be precise, it is not r

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #7 from Dominique d'Humieres 2011-08-14 13:20:27 UTC --- (In reply to comment #5) For the record, F95 and F2003 have a similar constraint, respectively: Constraint: A common-block-object shall not be a dummy argument, an allocatable

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 janus at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #5 from janus at gcc dot gnu.org 2011-08-14 12:07:55 UTC --- (In reply to comment #2) > ifort rejects the original test case with: > > error #6756: A COMMON block data object must not be an automatic object. [Z] > common n,z >

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #4 from janus at gcc dot gnu.org 2011-08-14 12:02:57 UTC --- (In reply to comment #3) > The relevant quote from the F08 std is probably: > > "C417 (R422) A type-param-value in a char-length shall be a colon, asterisk, > or > specificat

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 --- Comment #3 from janus at gcc dot gnu.org 2011-08-13 12:05:31 UTC --- (In reply to comment #2) > I assume this is an ice-on-invalid-code. The relevant quote from the F08 std is probably: "C417 (R422) A type-param-value in a char-length shall b

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 janus at gcc dot gnu.org changed: What|Removed |Added Keywords||ice-on-invalid-code Known

[Bug fortran/50070] Segmentation fault at size_binop_loc in fold-const.c

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50070 janus at gcc dot gnu.org changed: What|Removed |Added CC||janus at gcc dot gnu.org --- Co