This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [gfortran patch] PR 23661


On Thu, Sep 01, 2005 at 12:58:56AM +0200, Tobias Schl?ter wrote:
> Uttam Pawar wrote:
> > diff -urN gcc.mline/gcc/fortran/parse.c gcc.mine/gcc/fortran/parse.c
> > --- gcc.mline/gcc/fortran/parse.c	2005-08-31 10:49:55.000000000 -0700
> > +++ gcc.mine/gcc/fortran/parse.c	2005-08-31 11:51:35.000000000 -0700
> > @@ -249,6 +249,7 @@
> >  
> >      case 'p':
> >        match ("print", gfc_match_print, ST_WRITE);
> > +      match ("print fmt", gfc_match_print, ST_WRITE_FMT);
> >        match ("parameter", gfc_match_parameter, ST_PARAMETER);
> >        match ("pause", gfc_match_pause, ST_PAUSE);
> >        match ("pointer", gfc_match_pointer, ST_ATTR_DECL);
> 
> How is this supposed to work if the variable is not named "fmt"?  From a brief
> look at the code it seems that it should already be doing the right thing, but
> doesn't.  I've had a short look in the debugger (without your patch) and I'm
> not sure I understand what's happening.  I'll add more details in the PR.
> 

A quick look through the sources suggests the failure is coming
from match_io around line 2163.  These statements are ok.

  print *, yada
  print '(A)', yada
 
There is no allowance for a string as in

  print fmt


-- 
Steve


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]