This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/49791] [4.4/4.5/4.6/4.7 Regression] Formatted namelist reads fails with: Cannot match namelist object
- From: "quantum.analyst at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 20 Jul 2011 21:09:22 +0000
- Subject: [Bug libfortran/49791] [4.4/4.5/4.6/4.7 Regression] Formatted namelist reads fails with: Cannot match namelist object
- Auto-submitted: auto-generated
- References: <bug-49791-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49791
--- Comment #6 from Elliott Sales de Andrade <quantum.analyst at gmail dot com> 2011-07-20 21:09:20 UTC ---
(In reply to comment #3)
> If the bug reporter can, I think he should convert all the input files to the
> Fortran 90 syntax of namelists. However, one needs to be careful to not
> inadvertently to change the meaning (e.g. remove the wrong "(1)") and it might
> affect many files.
>
I can change the test suite, but since we also use the Intel and PGI compilers,
I wouldn't be able to guarantee other people won't get confused with this.
(In reply to comment #4)
>
> It's an undocumented bug^H^H^H extension.
>
> The undocumented extension cannot be flagged by any combination of
> -Wall, -Wextra, -fcheck=all, -Wsurprising and/or -std=f95,f2003,f2008.
Perhaps I am misreading it, but I thought it was actually documented at
http://gcc.gnu.org/onlinedocs/gfortran/Extensions-to-namelist.html
> Expanded namelist reads are permitted. This causes an error if -std=f95 is
> used. In the following example, the first element of the array will be given
> the value 0.00 and the two succeeding elements will be given the values 1.00
> and 2.00.
>
> &MYNML
> X(1,1) = 0.00 , 1.00 , 2.00
> /
>