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++/52597] [C++11] confusing diagnostics for invalid use of non-static member function in decltype Date: Fri, 24 Aug 2012 14:07:00 -0000 [thread overview] Message-ID: <bug-52597-4-3fTTyJY3Es@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52597-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52597 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|accepts-invalid, |diagnostic |rejects-valid, wrong-code | Status|UNCONFIRMED |NEW Last reconfirmed| |2012-08-24 Version|4.6.0 |4.7.1 Summary|[C++11] missing diagnostics |[C++11] confusing |for invalid use of |diagnostics for invalid use |non-static member function |of non-static member |in decltype |function in decltype Ever Confirmed|0 |1 Known to fail|4.3.2, 4.4.0, 4.5.0, 4.6.0 | --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-08-24 14:06:45 UTC --- OK, let's change it from an accepts-invalid with 4.6 to a diagnostic issue with 4.7
next prev parent reply other threads:[~2012-08-24 14:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-16 2:45 [Bug c++/52597] New: [C++11] missing " hstong at ca dot ibm.com 2012-03-16 9:55 ` [Bug c++/52597] " redi at gcc dot gnu.org 2012-03-29 1:05 ` hstong at ca dot ibm.com 2012-08-24 11:53 ` redi at gcc dot gnu.org 2012-08-24 12:43 ` hstong at ca dot ibm.com 2012-08-24 14:07 ` redi at gcc dot gnu.org [this message] 2013-03-27 10:06 ` [Bug c++/52597] [C++11] confusing " paolo.carlini at oracle dot com 2020-04-27 8:26 ` 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-52597-4-3fTTyJY3Es@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).