This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, fortran] PR20779 and PR20891 - allocation of STAT or specification variables in same call
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Paul Thomas <paulthomas2 at wanadoo dot fr>
- Cc: patch <gcc-patches at gcc dot gnu dot org>, "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>
- Date: Tue, 3 Oct 2006 12:31:21 -0700
- Subject: Re: [Patch, fortran] PR20779 and PR20891 - allocation of STAT or specification variables in same call
- References: <450D87A2.1040003@wanadoo.fr> <450ED555.7010000@wanadoo.fr>
On Mon, Sep 18, 2006 at 07:20:21PM +0200, Paul Thomas wrote:
> >
> >2006-09-17 Paul Thomas <pault@gcc.gnu.org>
> >
> > PR fortran/20779
> > PR fortran/20891
> > * resolve.c (find_sym_in_expr): New function that returns true
> > if a symbol is found in an expression.
> > (resolve_allocate_expr): Check whether the STAT variable is
> > itself allocated in the same statement. Use the call above to
> > check whether any of the allocated arrays are used in array
> > specifications in the same statement.
> >
> >2006-09-17 Paul Thomas <pault@gcc.gnu.org>
> >
> > PR fortran/20779
> > PR fortran/20891
> > * gfortran.dg/alloc_alloc_expr_1.f90: New test.
> >
Paul,
I think the patch is okay after you eliminate this little
chunk:
- if (ref2->u.ar.type == AR_ELEMENT)
- return SUCCESS;
+/* if (ref2->u.ar.type == AR_ELEMENT)
+ return SUCCESS;*/
--
Steve