This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/30239] duplicate data type assignment not detected
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Dec 2006 07:49:14 -0000
- Subject: [Bug fortran/30239] duplicate data type assignment not detected
- References: <bug-30239-13648@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from burnus at gcc dot gnu dot org 2006-12-18 07:49 -------
> This was a fix for a PR about a year ago - the std=gnu is meant, obviously, to
> enforce all versions of the standard on this. However, a number of other
> compilers did/do permit this wrinkle on the standard and it even appears in one
> of Meissner's examples.
Thus: Should we warn? Give an error (as ifort, NAG f95 and g95 do)? Or keep the
status quo where an error is given only for -pedantic and -std=f95/f2003 ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30239