[Bug fortran/91372] Error: Unclassifiable statement

2019-08-05 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91372

--- Comment #2 from Steve Kargl  ---
On Mon, Aug 05, 2019 at 06:44:31PM +, kargl at gcc dot gnu.org wrote:
> 
> The code is invalid.
> 
> Free-form source code requires whitespace after "DATA".
> 

So my reading to 

R837 data-stmt  is DATA data-stmt-set [ [ , ] data-stmt-set ] ...

may have been to strict.  The standard has

  A blank shall be used to separate names, constants, or labels
  from adjacent keywords, names, constants, or labels. 

The '(' isn't a name, constant, or label, so the blank may
be omitted.  Easy to fix.

[Bug fortran/91372] Error: Unclassifiable statement

2019-08-05 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91372

kargl at gcc dot gnu.org changed:

   What|Removed |Added

   Priority|P3  |P4
   Assignee|unassigned at gcc dot gnu.org  |kargl at gcc dot gnu.org
   Severity|normal  |trivial

[Bug fortran/91372] Error: Unclassifiable statement

2019-08-05 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91372

--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Mon Aug  5 19:24:31 2019
New Revision: 274122

URL: https://gcc.gnu.org/viewcvs?rev=274122&root=gcc&view=rev
Log:
2019-08-05  Steven g. Kargl  

PR fortran/91372
* decl.c (gfc_match_data): Allow an implied do-loop to nestle against
DATA.

2019-08-05  Steven g. Kargl  

PR fortran/91372
* gfortran.dg/pr91372.f90: New test.

Added:
trunk/gcc/testsuite/gfortran.dg/pr91372.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/decl.c
trunk/gcc/testsuite/ChangeLog

[Bug fortran/91372] Error: Unclassifiable statement

2019-08-05 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91372

kargl at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Target Milestone|--- |10.0

--- Comment #4 from kargl at gcc dot gnu.org ---
Fixed.  Sorry about the confusion.