[Bug libfortran/24459] gfortran namelist problem

2006-05-20 Thread jvdelisle at gcc dot gnu dot org
--- Comment #16 from jvdelisle at gcc dot gnu dot org 2006-05-20 07:15 --- Subject: Bug 24459 Author: jvdelisle Date: Sat May 20 07:14:50 2006 New Revision: 113924 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113924 Log: 2006-05-20 Jerry DeLisle <[EMAIL PROTECTED]>

[Bug libfortran/24459] gfortran namelist problem

2006-05-15 Thread patchapp at dberlin dot org
--- Comment #15 from patchapp at dberlin dot org 2006-05-15 19:30 --- Subject: Bug number PR24459 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2006-05/msg0.html -- http://gcc.gnu.org/bugzilla/s

[Bug libfortran/24459] gfortran namelist problem

2006-05-02 Thread ed at eh3 dot com
--- 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.

[Bug libfortran/24459] gfortran namelist problem

2006-05-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2006-05-02 00:02 --- Patch here: http://gcc.gnu.org/ml/fortran/2006-05/msg0.html Waiting for approval -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459

[Bug libfortran/24459] gfortran namelist problem

2006-04-22 Thread jvdelisle at gcc dot gnu dot org
-- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |jvdelisle at gcc dot gnu dot |dot org

[Bug libfortran/24459] gfortran namelist problem

2005-12-04 Thread jvdelisle at gcc dot gnu dot org
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2005-12-04 23:11 --- We just had a discussion regarding another similar problem. The maintainers need to come to some concensus on the behavior of some compiler flags such as -std=f95 and -pedantic. Once that is settled then we can

[Bug libfortran/24459] gfortran namelist problem

2005-12-04 Thread ed at eh3 dot com
--- 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:

[Bug libfortran/24459] gfortran namelist problem

2005-11-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2005-11-25 19:44 --- I am reopening this PR because I recieved information that the behavior is a pre F90 feature commonly used before array triplet notation was introduced. I also found that it is supported in g77. So we treatthis

[Bug libfortran/24459] gfortran namelist problem

2005-11-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #9 from jvdelisle at gcc dot gnu dot org 2005-11-24 17:25 --- After going to comp.lang.fortran I determined this is not a bug and gfortran is correctly handling the given namelist. To get desired behavior use array qualifiers with array triplet notation. -- jvdelisle at

[Bug libfortran/24459] gfortran namelist problem

2005-11-24 Thread ed at eh3 dot com
--- 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.

[Bug libfortran/24459] gfortran namelist problem

2005-11-23 Thread jvdelisle at gcc dot gnu dot org
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-24 07:21 --- This is not a bug. Gfortran is complying with F95 namelist read requirements. This would be an enhancement or extension. The work around is to use correct array triplets in the array qualifiers for namelist read

[Bug libfortran/24459] gfortran namelist problem

2005-11-02 Thread ed at eh3 dot com
--- 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

[Bug libfortran/24459] gfortran namelist problem

2005-11-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2005-11-02 06:41 --- I will be looking at this sometime soon. If this is high priority I will shift from DATE and TIME intrinsics to this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459

[Bug libfortran/24459] gfortran namelist problem

2005-10-29 Thread jvdelisle at gcc dot gnu dot org
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2005-10-30 02:59 --- OK I have a patch for the segfault I was seeing and now I see the error the OP discusses. I will continue on that as soon as I get the other bug fix submitted for review. (I will have to create a new PR for the

[Bug libfortran/24459] gfortran namelist problem

2005-10-25 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2005-10-26 02:44 --- With the first case given, I get a segfault on i686-pc-linux-gnu. gcc version 4.1.0 20051025 (experimental) $ cat diag.nml &DIAGS NAMES = 'ETAN' 'ETANSQ' 'DETADT2' 'PHIBOT' 'PHIBOTSQ' '' '' '' '' '' '' '' '' ''

[Bug libfortran/24459] gfortran namelist problem

2005-10-21 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-10-21 22:27 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added OtherBugsDependingO|