public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95725] Confusing error diagnostic in an invalid template Date: Wed, 17 Jun 2020 18:58:50 +0000 [thread overview] Message-ID: <bug-95725-4-bTdurujfm5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95725-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95725 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- The diagnostic is usually for false positive/negative warnings or wrong information in diagnostic messages. It's not normally used for internal compiler errors. But I don't see an ICE on trunk with this test case, just errors (so diagnostic would seem appropriate). At the same time, the latest GCC output seems reasonable. Clang prints something similar: pr95725.C:1:20: error: expected expression template <decltype(= ; ^ pr95725.C:1:22: error: expected expression template <decltype(= ; ^ pr95725.C:1:22: error: expected ',' or '>' in template-parameter-list pr95725.C:1:22: warning: declaration does not declare anything [-Wmissing-declarations] 1 warning and 3 errors generated. I'm not sure there's a lot to improve here.
next prev parent reply other threads:[~2020-06-17 18:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-17 17:02 [Bug c++/95725] New: " haoxintu at gmail dot com 2020-06-17 17:43 ` [Bug c++/95725] " marxin at gcc dot gnu.org 2020-06-17 17:49 ` haoxintu at gmail dot com 2020-06-17 18:58 ` msebor at gcc dot gnu.org [this message] 2020-06-17 23:49 ` mpolacek at gcc dot gnu.org 2020-06-17 23:57 ` redi at gcc dot gnu.org 2020-06-18 1:51 ` haoxintu at gmail dot com 2020-06-18 6:23 ` haoxintu at gmail dot com 2020-06-18 8:34 ` rguenth at gcc dot gnu.org 2020-06-18 11:26 ` redi at gcc dot gnu.org 2020-06-18 11:31 ` redi at gcc dot gnu.org 2024-05-09 9:08 ` redi 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-95725-4-bTdurujfm5@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).