public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95724] bogue error : "expected '{' before ')' token" Date: Thu, 18 Jun 2020 12:25:17 +0000 [thread overview] Message-ID: <bug-95724-4-6f9dJBK5r9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95724-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95724 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #6) > (In reply to Richard Biener from comment #4) > > Note the testcase does not ICE so ice-on-invalid is wrong. It's really > > a diagnostic only. If we want sth extra to distinguish error diagnostics > > from warning diagnostics then we should add one (can't come up with a good > > name right now) > > It's like a weaker form of error-recovery but for cases that don't ICE. error-recovery is fine then I guess since it doens't imply ICEing. We use the combo of ice-on-invalid-code, error-recovery for that. But indeed the description says 'use only for ice-on-invalid-code' ... > cascading-errors maybe.
next prev parent reply other threads:[~2020-06-18 12:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-17 16:45 [Bug c++/95724] New: " haoxintu at gmail dot com 2020-06-17 17:43 ` [Bug c++/95724] " marxin at gcc dot gnu.org 2020-06-17 17:54 ` haoxintu at gmail dot com 2020-06-17 18:58 ` marxin at gcc dot gnu.org 2020-06-18 8:33 ` rguenth at gcc dot gnu.org 2020-06-18 8:37 ` marxin at gcc dot gnu.org 2020-06-18 11:37 ` redi at gcc dot gnu.org 2020-06-18 12:25 ` rguenth at gcc dot gnu.org [this message] 2022-01-07 2:35 ` [Bug c++/95724] error message could be improved in the cascading error case pinskia 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-95724-4-6f9dJBK5r9@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: linkBe 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).