------- Comment #12 from kargl at gcc dot gnu dot org 2010-02-17 15:57 -------
(In reply to comment #10)
> (NAG f95 v5.1 and g95 reject it unconditionally; ifort allows it by default
> but
> rejects it with -stand f95 or -stand f03.)
>
> I think one should really send a interpretation request.
I already contacted Dan Nagle. I'll write up the issue
today and send it to whom.
>
> A patch would be the following. What about POINTERs?
>
See comment #2.
> Index: symbol.c
> ===================================================================
> --- symbol.c (Revision 156815)
> +++ symbol.c
> @@ -389,2 +389,10 @@ check_conflict (symbol_attribute *attr,
>
> + if (attr->in_namelist && attr->allocatable)
> + {
> + a1 = in_namelist;
> + a2 = allocatable;
> + standard = GFC_STD_F2003;
> + goto conflict_std;
> + }
> +
> /* Check for attributes not allowed in a BLOCK DATA. */
> @@ -493,3 +501,2 @@ check_conflict (symbol_attribute *attr,
> conf (in_namelist, pointer);
> - conf (in_namelist, allocatable);
>
This isn't sufficient. See comment #2. During a namelist read/write,
gfortran needs to check that the allocatable array is allocated and
that a pointer is associated with a target.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43062
