--- Comment #3 from dfranke at gcc dot gnu dot org 2009-12-11 21:44 ---
(In reply to comment #2)
> I wonder why this is not caught in parse.c's verify_st_order; the error
> message there is much nicer
Because it seems that verify_st_order is not called for every accepted
statement. In
--- 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_erro
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |enhancement
Status|UNCONFIRMED |NEW
