--- Comment #4 from fxcoudert at gcc dot gnu dot org 2008-03-05 09:43
---
(Hey, a UCL colleague! Small world...)
I'm closing this bug as FIXED in 4.2.0. If you have any trouble upgrading to
the newest compiler versions, feel free to ask for help on the gfortran
mailing-list: [EMAIL PRO
--- 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
--- Comment #2 from kargl at gcc dot gnu dot org 2008-03-04 17:15 ---
This compiles with 4.2.3 and 4.3.0 (aka trunk). In that you are using
4.1.2, I doubt anyone with fix this bug in that branch. I'll suggest
that an upgrade to a newer version of gfortran is in order.
This bug should
--- Comment #1 from s dot binnie at ucl dot ac dot uk 2008-03-04 15:15
---
Created an attachment (id=15260)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15260&action=view)
testcase for above bug
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35459
