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++/17971] New: [3.4/4.0 regression] Invalid default parameter not diagnosed. Date: Wed, 13 Oct 2004 09:38:00 -0000 [thread overview] Message-ID: <20041013093830.17971.reichelt@gcc.gnu.org> (raw) Since PR 16929 got a little confusing, I'm opening a new PR for the following problem: Since gcc 3.4.0 we accept the following invalid code snippet. The invalid default parameter "a" is not even diagnosed at instantiation time. (This is different from PT 17011 - also a spin-off from PR16929 - which is just a QoI issue.) =========================================== template<typename> struct A {}; template<typename T> struct B { A<T> a; void foo(A<T> = a); }; template struct B<int>; =========================================== With 3.3.5 and before we got a decent error message: bug.cc:7: error: invalid use of member `B<T>::a' -- Summary: [3.4/4.0 regression] Invalid default parameter not diagnosed. Product: gcc Version: 3.4.3 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,mark at codesourcery dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17971
next reply other threads:[~2004-10-13 9:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-13 9:38 reichelt at gcc dot gnu dot org [this message] 2004-10-13 12:22 ` [Bug c++/17971] " pinskia at gcc dot gnu dot org 2004-10-13 12:50 ` bangerth at dealii dot org 2004-11-01 0:46 ` mmitchel at gcc dot gnu dot org 2004-11-28 6:03 ` lerdsuwa at gcc dot gnu dot org 2004-12-03 10:25 ` lerdsuwa at gcc dot gnu dot org 2004-12-04 7:07 ` lerdsuwa 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=20041013093830.17971.reichelt@gcc.gnu.org \ --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).