------- Comment #4 from burnus at gcc dot gnu dot org 2008-03-05 17:55 ------- Thanks for the report. I can reproduce the problem with 4.2.3, however, it seems to be fixed in GCC/gfortran 4.3.0rc2 (and 4.4.0) - and as Daniel noted it used to worked with 4.1.3.
GCC 4.3.0 is supposted to be released at the end of this week (currently, we have release candidate 2). Any chance that you could upgrade your GCC and try again? Despite being a regression, I'm not sure it will be fixed soon as we need to find the fix first. Binaries and a description how to build GCC from source can be found at http://gcc.gnu.org/wiki/GFortranBinaries Depending on your Linux distribution, they might have already experimental GCC 4.3.0 packages somewhere. Changelog: http://gcc.gnu.org/gcc-4.3/changes.html -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|4.2.4 |4.1.3 4.2.2 Known to work|4.1.2 4.3.0 4.4.0 |4.3.0 4.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35475