public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32365] Better error message for specification statement in executable section
Date: Wed, 20 Jun 2007 16:39:00 -0000	[thread overview]
Message-ID: <20070620163904.4000.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32365-13404@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2007-06-20 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16  8:52 [Bug fortran/32365] New: OpenMP: " burnus at gcc dot gnu dot org
2007-06-20 16:23 ` [Bug fortran/32365] " jakub at gcc dot gnu dot org
2007-06-20 16:39 ` burnus at gcc dot gnu dot org [this message]
2007-07-03 10:26 ` [Bug fortran/32365] " fxcoudert at gcc dot gnu dot org
2009-12-11 21:44 ` dfranke at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070620163904.4000.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).