Bug 430528 - Fortran runtime error with a correct format string
Fortran runtime error with a correct format string
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
All All
low Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-01-28 11:29 EST by Ben Webb
Modified: 2009-01-09 00:52 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:52:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
test.F90 (1.42 KB, application/octet-stream)
2008-01-28 11:29 EST, Ben Webb
no flags Details

  None (edit)
Description Ben Webb 2008-01-28 11:29:12 EST
Description of problem:
Our large Fortran 90 software has recently started failing some of its unit
tests with the following runtime error:
Fortran runtime error: Expected INTEGER for item 4 in formatted transfer, got REAL

An examination of the code shows that the format string and arguments are
correct (and it works fine with other compilers). The error message is also
either inconsistent or incorrect (item 4 looks like the second f8.2 format to
me, while the caret is pointing to the second item). I managed to reduce the
problem down to a simple example, although given that the problem mysteriously
disappeared when seemingly unrelated variables and code sections were removed,
it suggests a bug in the generated code or runtime checks. (Our unit tests also
used to work with the same gcc version, although nearby parts of our code were
changed just before the tests started failing.)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Get test.F90 (attached).
2. % gfortran test.F90
3. % ./a.out
Actual results:
Program prints the following output:
Fortran runtime error: Expected INTEGER for item 4 in formatted transfer, got REAL
(last line appears to be garbage, but is entered here verbatim as seen on my

Expected results:
Program runs without complaining about the format string, e.g. when compiled
with ifort the following output is seen:
       0    0.00    0.00       0       0
(Note that this is a cut down example, so I don't bother to initialize any of
these variables. So the output may be garbage too. But you shouldn't get the
format string error.)

Additional information:
I guess this an upstream problem, since the same program compiled with gfortran
4.2.2 on an Intel MacBook Pro (OS X Leopard) exhibits the same problem.
Comment 1 Ben Webb 2008-01-28 11:29:12 EST
Created attachment 293168 [details]
Comment 2 Bug Zapper 2008-11-26 04:36:15 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Ben Webb 2008-11-30 13:54:19 EST
I guess this bug has been fixed upstream, since I can no longer reproduce the problem with Fedora 9 (gcc-gfortran-4.3.0-8.i386).
Comment 4 Bug Zapper 2009-01-09 00:52:19 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.