public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/42218] New: [4.5 Regression] Broken diagnostic: 'tree_vec' not supported by pp_c_expression Date: Sun, 29 Nov 2009 15:31:00 -0000 [thread overview] Message-ID: <bug-42218-1771@http.gcc.gnu.org/bugzilla/> (raw) A broken diagnostic is issued for the following invalid code snippet on trunk: ================================ template<int> struct A { template<int> struct B; }; int i = A<0>::B<0>::X::Y; ================================ bug.cc:6:21: error: 'A<0>::B<#'tree_vec' not supported by pp_c_expression#, #'tree_vec' not supported by pp_c_expression#>::X' has not been declared GCC 4.3.x and 4.4.x issue a sensible error message: bug.cc:6: error: 'A::B::X' has not been declared GCC 4.2.x issues an even better error message: bug.cc:6: error: 'struct A<0>::B<0>::X' has not been declared -- Summary: [4.5 Regression] Broken diagnostic: 'tree_vec' not supported by pp_c_expression Product: gcc Version: 4.5.0 Status: UNCONFIRMED Keywords: diagnostic, monitored Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42218
next reply other threads:[~2009-11-29 15:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-29 15:31 reichelt at gcc dot gnu dot org [this message] 2009-11-29 15:31 ` [Bug c++/42218] " reichelt at gcc dot gnu dot org 2009-11-29 15:42 ` rguenth at gcc dot gnu dot org 2009-12-03 17:22 ` dodji at gcc dot gnu dot org 2009-12-03 18:25 ` dodji at gcc dot gnu dot org 2009-12-04 7:39 ` dodji at gcc dot gnu dot org 2009-12-04 7:40 ` dodji at gcc dot gnu dot 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-42218-1771@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).