http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43179
Mikael Morin changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43179
--- Comment #9 from Dominique d'Humieres 2012-02-05
17:37:33 UTC ---
With trunk at revision 183904 or with 4.6.2, I get
pr43179.f90:6.14:
if (allocated(foo(1)%a)) call abort()
1
Error: 'array' argument of 'allocated' intrinsic at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43179
--- Comment #8 from Daniel Franke 2010-12-30
02:39:58 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > > OK for trunk with the usual embellishments of ChangeLogs and testcase?
> > >
> > > Yes, if you
--- Comment #7 from pault at gcc dot gnu dot org 2010-07-18 07:09 ---
(In reply to comment #2)
> (In reply to comment #1)
> > This fixes it and regtests.
> > + if (array->expr_type != EXPR_VARIABLE && array->expr_type !=
> > EXPR_FUNCTION)
>
> The patch looks OK, but actually I fail
--- Comment #6 from dfranke at gcc dot gnu dot org 2010-07-15 21:57 ---
Spin-off: PR44960
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43179
--- Comment #5 from pault at gcc dot gnu dot org 2010-06-24 15:42 ---
(In reply to comment #4)
> (In reply to comment #2)
> > > OK for trunk with the usual embellishments of ChangeLogs and testcase?
> >
> > Yes, if you have an example for EXPR_FUNCTION - otherwise I would claim that
> >
--- Comment #4 from dfranke at gcc dot gnu dot org 2010-05-18 22:44 ---
(In reply to comment #2)
> > OK for trunk with the usual embellishments of ChangeLogs and testcase?
>
> Yes, if you have an example for EXPR_FUNCTION - otherwise I would claim that
> EXPR_VARIABLE is enough.
Paul,
--- Comment #3 from burnus at gcc dot gnu dot org 2010-02-26 10:26 ---
> gfortran already bails out with:
> Error: Allocate-object at (1) is not a nonprocedure pointer
> or an allocatable variable
If you are already patching, can you also improve the wording for this old
error messa
--- Comment #2 from burnus at gcc dot gnu dot org 2010-02-26 07:54 ---
(In reply to comment #1)
> This fixes it and regtests.
> + if (array->expr_type != EXPR_VARIABLE && array->expr_type !=
> EXPR_FUNCTION)
The patch looks OK, but actually I fail to see when an EXPR_FUNCTION is vali
--- Comment #1 from pault at gcc dot gnu dot org 2010-02-26 07:35 ---
This fixes it and regtests.
Index: gcc/fortran/check.c
===
*** gcc/fortran/check.c (revision 157061)
--- gcc/fortran/check.c (working copy)
*
10 matches
Mail list logo
