[Bug fortran/58043] [OOP] Incorrect behaviour of polymorphic array

2017-10-27 Thread marco at hulten dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58043

Marco van Hulten  changed:

   What|Removed |Added

 CC||marco at hulten dot org

--- Comment #6 from Marco van Hulten  ---
The problem still exists in GCC 5.4.0, which was released in June 2016.

In what version is this fixed?

[Bug fortran/52512] Cannot match namelist object name

2012-03-07 Thread marco at hulten dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52512

--- Comment #3 from Marco van Hulten marco at hulten dot org 2012-03-07 
12:15:36 UTC ---
This work-around of changing all entries to tracer(N:N) indeed works, in both
the test case as for my original code where I found the problem.  That is the
NEMO 3.1 ocean model, with namelist_top containing 26 tracer entries of a
larger structure, but similar to the test case.


[Bug fortran/52512] New: Cannot match namelist object name

2012-03-06 Thread marco at hulten dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52512

 Bug #: 52512
   Summary: Cannot match namelist object name
Classification: Unclassified
   Product: gcc
   Version: 4.4.6
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: ma...@hulten.org


Created attachment 26843
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=26843
namelist

During run-time I get the error Cannot match namelist object name.  This
*might* be the same as #51825, but that one is about writing to the namelist,
while this is about reading.  To not make any confusion if it is indeed
different, I created a new bug.  I compiled the following code with gfortran
4.4.6 (on RHEL6.2):

PROGRAM testje
  IMPLICIT NONE

  INTEGER :: getal, jn
  TYPE PTRACER
 CHARACTER(len = 8)  :: sname  !: short name
 LOGICAL :: lini   !: read in a file or not
  END TYPE PTRACER
  TYPE(PTRACER) , DIMENSION(3) :: tracer
  NAMELIST/namtoptrc/  getal,tracer

  ! Standard values
  getal = 
  DO jn = 1, 3
 tracer(jn)%sname = 'DEFAULT_NAME'
 tracer(jn)%lini = .FALSE.
  END DO

  open (99, file='nml.dat')
  read (99, nml=namtoptrc)
  write (*, nml=namtoptrc)
END PROGRAM testje

I enclosed the namelist.  It runs fine with ifort.


[Bug fortran/46010] I/O: Namelist-reading bug

2010-11-02 Thread marco at hulten dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010

--- Comment #14 from Marco van Hulten marco at hulten dot org 2010-11-02 
20:29:17 UTC ---
I succesfully compiled the trunk version and hereafter compiled and executed my
test case without problems (giving the righ results).  I am looking forward to
the backport into gcc 4.4.


[Bug fortran/46010] I/O: Namelist-reading bug

2010-10-26 Thread marco at hulten dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010

--- Comment #10 from Marco van Hulten marco at hulten dot org 2010-10-26 
09:13:28 UTC ---
On Tue, 26 Oct 2010 01:37:08 + jvdelisle wrote:
 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010
 
 --- Comment #9 from Jerry DeLisle jvdelisle at gcc dot gnu.org
 2010-10-26 01:37:04 UTC --- Created attachment 22156
   -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=22156
 Patch to fix this.
 
 I think my email service is out. I attach the patch here for review.
 It may show up on the list.  I tried sending it three times.

Thank you for the patch.

I have no time right now to apply and check the patch, but maybe in the
weekend.

Cheers,

Marco


[Bug fortran/46010] I/O: Namelist-reading bug

2010-10-14 Thread marco at hulten dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010

--- Comment #5 from Marco van Hulten marco at hulten dot org 2010-10-14 
18:15:59 UTC ---
(In reply to comment #4)
 [...]
 The issue is really the .true. (T,true, .false., F, false). If the
 last item (in the namelist and in the derived type) is an integer or a string
 it works.

No, that doesn't seem to be the issue.  I tried both your minimal test case as
well as my test case, with an added character as well as an added number, but
all give the following result:

ma...@graviton testje $ gfortran -std=f2003 test.f90
ma...@graviton testje $ ./a.out 
NAMTOPTRC
 TRACER(1)%SNAME=Aa,
 TRACER(1)%LINI=T,
 TRACER(1)%GETAL=  1,
 TRACER(2)%SNAME=Bb,
 TRACER(2)%LINI=T,
 TRACER(2)%GETAL=  1,
 TRACER(3)%SNAME=Cc,
 TRACER(3)%LINI=T,
 TRACER(3)%GETAL=  1,
 /
ma...@graviton testje $ gfortran test.f90 
ma...@graviton testje $ ./a.out 
At line 13 of file test.f90 (unit = 99, file = 'nml.dat')
Fortran runtime error: Bad data for namelist object tracer%getal


[Bug fortran/46010] New: reading of structure

2010-10-13 Thread marco at hulten dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010

   Summary: reading of structure
   Product: gcc
   Version: 4.5.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: ma...@hulten.org


Created attachment 22032
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=22032
program with the struct and input namelist file

I compiled the NEMO ocean model (revision 1162) with gfortran.  If I now run
the program, I get nonsense (random memory) data written in the 2nd, 4th, 6th
etc. ocean tracer entry in my output.  The relevant code and namelist file
needed for compilation and the relevant output are attached to this e-mail.

This problem arises with gfortran 4.1.2 (RHEL), 4.4.5 (Debian) and 4.5.1
(Arch), but it doesn't with the Intel Fortran Compiler (ifort).  Please let me
know if you need other information.