------- Comment #3 from burnus at gcc dot gnu dot org 2008-03-04 21:48 ------- First of all, I would like to thank your for the bug report.
While the bug is present in 4.1, it has been fixed meanwhile and 4.2.3, 4.3.0 and 4.4.0 work. The GCC policy is essentially only to backport fixes to older version if it is a regression thus I think this will not be fixed in 4.1.x. (Also due to lack of resources. Besides, I think Red Hat will not provide a newer GCC 4.1.x.) I would therefore suggest that you update to a newer GCC. The latest released GCC is 4.2.3 but GCC 4.3.0 can be expected soon. (Currently: 4.3.0 release candidate 2.) To my knowledge Red Hat plans to use GCC/gfortran 4.3.0 for their upcoming Enterprise product and the next Fedora version; I would not be surprised if they already provide Fedora RPMs. Otherwise, you can compile gfortran yourself or use the binaries available from: http://gcc.gnu.org/wiki/GFortranBinaries -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |4.1.2 4.1.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35459
