public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43711] Unformitive error message for two NOWAIT in OpenMP directive
Date: Fri, 07 May 2010 17:24:00 -0000	[thread overview]
Message-ID: <20100507172400.7437.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43711-14710@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from dfranke at gcc dot gnu dot org  2010-05-07 17:23 -------
In openmp.c (gfc_match_omp_end_nowait), we match "nowait" and end-of-string. If
there's anything but whitespace after the nowait, the match is rejected.

With "nowait" being rejected, parse.c (match_word) rejects the whole matching
sequence, { "end sections" "nowait" end-of-string } and returns to the last
known locus, here just after the "$omp".

67  if (m != MATCH_YES)
68    {
69      gfc_current_locus = *old_locus;
70      reject_statement ();
71    }

If line 69 is removed, one gets:

pr43711.f90:8.31:

      !$omp end sections nowait nowait
                               1
Error: Unclassifiable OpenMP directive at (1)

But everything else is broken ^^


This is not specific for nowait, but for all OpenMP related things that
explicitly check for end-of-string.


I believe, this is eventually the same as PR32365.


-- 

dfranke at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  GCC build triplet|x86_64-suse-linux           |
   GCC host triplet|x86_64-suse-linux           |
 GCC target triplet|x86_64-suse-linux           |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43711


  reply	other threads:[~2010-05-07 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 20:42 [Bug fortran/43711] New: " longb at cray dot com
2010-05-07 17:24 ` dfranke at gcc dot gnu dot org [this message]
2010-05-07 17:42 ` [Bug fortran/43711] " dfranke at gcc dot gnu dot org
2010-05-11 16:45 ` dfranke at gcc dot gnu dot org
2010-05-11 16:46 ` dfranke at gcc dot gnu dot org
2010-05-11 16:47 ` 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=20100507172400.7437.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).