------- Comment #2 from burnus at gcc dot gnu dot org 2007-06-20 16:39 -------
> There is nothing special about ST_OMP_THREADPRIVATE here, the Fortran parser
> as whole behaves this way.
Sorry for missing that.
> what perhaps could be done is e.g. adding something like
> case_decl:
> gfc_error ("%s statement can't appear after the first executable statement
I wonder why this is not caught in parse.c's verify_st_order; the error message
there is much nicer:
gfc_error ("%s statement at %C cannot follow %s statement at %L",
gfc_ascii_statement (st),
gfc_ascii_statement (p->last_statement), &p->where);
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|openmp |
Summary|OpenMP: Better error message|Better error message for
|for specification statement |specification statement in
|in executable section |executable section
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32365
