--- Comment #6 from pault at gcc dot gnu dot org 2009-04-06 11:07 ---
Fixed on trunk and 4.4
Thanks for the report
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #5 from pault at gcc dot gnu dot org 2009-03-28 17:39 ---
(In reply to comment #4)
Not so - this was the wrong message for another commit. This fix is on the
way.
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36528
--- Comment #4 from pault at gcc dot gnu dot org 2009-03-28 17:08 ---
Subject: Bug 36528
Author: pault
Date: Sat Mar 28 17:08:25 2009
New Revision: 145196
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145196
Log:
2009-02-13 Paul Thomas
PR fortran/36703
PR fo
--- Comment #3 from pault at gcc dot gnu dot org 2009-02-13 21:12 ---
Subject: Bug 36528
Author: pault
Date: Fri Feb 13 21:12:34 2009
New Revision: 144164
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=144164
Log:
2009-02-13 Paul Thomas
PR fortran/36703
PR fo
--- Comment #2 from pault at gcc dot gnu dot org 2009-02-11 15:08 ---
This fixes the bug. I need to look at the passing of Cray pointers in general
because it looks a bit shakey to me.
trans-expr.c:
2626c2626,2637
< if (fsym && fsym->attr.value)
---
> if (fsym
--- Comment #1 from burnus at gcc dot gnu dot org 2008-06-13 16:54 ---
For gfortran documentation, see:
http://gcc.gnu.org/onlinedocs/gfortran/Cray-pointers.html#Cray-pointers
a) If used directly, the tree is wrong (see dump), but it works nonetheless
(I somehow have not to realize t
