public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105547] No further "Unclassifiable statement" after the first one if multiple syntax errors.
Date: Tue, 10 May 2022 11:58:58 +0000	[thread overview]
Message-ID: <bug-105547-4-pLyKXbTDO1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105547-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105547

--- Comment #1 from Mikael Morin <mikael at gcc dot gnu.org> ---
In parse.cc, we avoid emitting an error if an other has been emitted.
But it uses the total error count, not the number of errors since we started
matching the current statement.

597  if (!gfc_error_check ())
598    {
599      int ecnt;
600      gfc_get_errors (NULL, &ecnt);
601      if (ecnt <= 0)
602        gfc_error_now ("Unclassifiable statement at %C");
603    }

  reply	other threads:[~2022-05-10 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:51 [Bug fortran/105547] New: " mikael at gcc dot gnu.org
2022-05-10 11:58 ` mikael at gcc dot gnu.org [this message]
2024-03-19 16:30 ` [Bug fortran/105547] " mikael at gcc dot gnu.org
2024-03-20  3:24 ` kargl at gcc dot gnu.org
2024-03-21 17:07 ` mikael at gcc dot gnu.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=bug-105547-4-pLyKXbTDO1@http.gcc.gnu.org/bugzilla/ \
    --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).