[Bug libfortran/24459] gfortran namelist problem
--- Comment #14 from ed at eh3 dot com 2006-05-02 16:20 --- Hi Jerry, I just re-ran the test case in this bug report and some other examples from our oceanic/atmospheric model (mitgcm.org) using gfortran which was checked out at about 12:30am (May 2) with: svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc and with your patch as described at: http://gcc.gnu.org/ml/fortran/2006-05/msg0.html applied. The good news (for me!) is that gfortran now works nicely (for every test that I've run so far) with this "old" (pre-F90) namelist syntax. I'll continue to test it. Thank you so much for chasing after this feature request and getting it implemented. Your time/effort is very much appreciated! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] gfortran namelist problem
--- Comment #8 from ed at eh3 dot com 2005-11-24 16:26 --- Hi Jerry, thank you for looking into this issue and clarifing it! The use of correct array triplets is a very quick and easy thing for us to do. And its certainly a good idea to follow the Fortran standard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] gfortran namelist problem
--- Comment #11 from ed at eh3 dot com 2005-12-04 19:54 --- Thank you for re-opening this bug! In an attempt to make our model (http://mitgcm.org) as portable as possible, we tried switching the namelist syntax from the older Fortran77 to F90 "triplets" and discovered the following: "old style" Fortran77: eg.: astring(1,1) = 'name1 ', 'name2 ', 'name3 ' This syntax works with basically *EVERY* Fortran77 compiler that we can get our hands on including g77, Sun, IBM xlf, PGI (pgif77), and Intel. But it fails with gfortran. "new-style F90 triplets": eg.: astring(1:3,1) = 'name1 ', 'name2 ', 'name3 ' This works with some Fortran77 compilers including g77 and Intel but it fails with others including PGI (pgf77). So I would again like to humbly request (or is it beg?!) that this long-standing g77 feature be included with gfortran. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug fortran/24459] New: gfortran namelist regression
I don't know if this is an actual regression but using gcc-4.0.2 built with: $ ../gcc-4.0.2/configure --prefix=/opt/gcc-4.0.2 \ --enable-languages=c,c++,f95 --program-suffix=-4.0.2 the program: $ cat diag.f program diag INTEGER nd PARAMETER ( nd = 5 ) CHARACTER*(8) names(nd,nd) NAMELIST / diags / names OPEN(UNIT=20,FILE='diag.nml',STATUS='OLD') READ(20,NML=diags) WRITE(*,NML=diags) STOP END will work with: $ cat diag.nml &DIAGS NAMES = 'ETAN' 'ETANSQ' 'DETADT2' 'PHIBOT' 'PHIBOTSQ' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''/ but fails with the message: $ ./diag At line 7 of file diag.f Fortran runtime error: Cannot match namelist object name 'etansq when reading: $ cat diag.nml &diags names(1,1) = 'ETAN','ETANSQ ','DETADT2 ','PHIBOT ','PHIBOTSQ', / The reason that it appears to be a regression is that both namelist files work nicely with basically all g77 versions shipped in recent years and with a large number of both past and present commercial Fortran compilers including Intel v5--v9, PGI, IBM xlf, and Sun. In my (humble!) opinion, it would be a shame if the namelist indexing ("implicit" indexing?) is lost since large namelist files are more legible using it. And, existing namelist files will require a fairly substantial amount of editing to convert between the two types of formatting. -- Summary: gfortran namelist regression Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ed at eh3 dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug fortran/24459] gfortran namelist regression
--- Comment #1 from ed at eh3 dot com 2005-10-20 19:53 --- The same error happens using gcc from cvs today (2005-10-20). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
[Bug libfortran/24459] gfortran namelist problem
--- Comment #6 from ed at eh3 dot com 2005-11-02 13:12 --- Hi jvdelisle, I'm not sure if it qualifies as "high priority" but it is one of the few (only?) gfortran bugs that we've encountered with the MITgcm fluid flow and transport model (http://mitgcm.org). If it helps, I'll be happy to test your fixes, do weekly testing with new versions of gfortran and our model, etc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459