public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57883] Feature request: better diagnostic for unknown type Date: Tue, 28 Sep 2021 10:48:15 +0000 [thread overview] Message-ID: <bug-57883-4-zpDmj2FmbH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57883-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57883 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- A test had to be changed due to the new (much better) diagnostic: https://gcc.gnu.org/git/?p=gcc.git;a=blobdiff;f=gcc/testsuite/g%2B%2B.dg/parse/saved1.C;h=1deaa93f516894d4757fc8671d630dcbfedaf4f6;hp=979a05676d2069911eb8c47c994ddf2fc4fb4ab8;hb=f9c80eb12c58126a94ad869380af5b88b752c06f;hpb=99585d88a090b4c5b7791f7ab62f70eb37b748fa
next prev parent reply other threads:[~2021-09-28 10:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-11 21:06 [Bug c++/57883] New: " dushistov at mail dot ru 2013-11-09 22:29 ` [Bug c++/57883] " pinskia at gcc dot gnu.org 2021-09-28 9:53 ` pinskia at gcc dot gnu.org 2021-09-28 10:47 ` redi at gcc dot gnu.org 2021-09-28 10:48 ` redi at gcc dot gnu.org [this message] 2021-09-28 19:12 ` 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-57883-4-zpDmj2FmbH@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).