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: Thu, 21 Mar 2024 17:07:03 +0000	[thread overview]
Message-ID: <bug-105547-4-pKHVyDWl4Q@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

Mikael Morin <mikael at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to kargl from comment #3)
> (In reply to Mikael Morin from comment #2)
> > Created attachment 57739 [details]
> > Patch fixing the problem
> > 
> > This small patch fixes the problem.
> > Unfortunately allowing more errors seems counter-productive here.
> > As seen in the testsuite changes, the additional errors have little value,
> > and add more noise than anything else.
> > I'm tempted to close this as WONTFIX.
> 
> I like your approach to limit the run-on errors.
> 
Well, the intent of this PR was on the contrary to avoid silent errors.

> I am, however, of the mind that if gfortran gets to the
> "Unclassifiable error" message, that perhaps, this should be
> a fatal error.
I guess one can find cases where later errors are useless noise, and cases
where they remain useful and are not caused by bad error recovery.

Anyway, I'm closing this.

      parent reply	other threads:[~2024-03-21 17:07 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 ` [Bug fortran/105547] " mikael at gcc dot gnu.org
2024-03-19 16:30 ` 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 [this message]

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-pKHVyDWl4Q@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).