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++/54913] [4.8 Regression] '#'indirect_ref' not supported by dump_decl#<declaration error>' is not a member of 'E' Date: Fri, 12 Oct 2012 17:02:00 -0000 [thread overview] Message-ID: <bug-54913-4-jQIdkEHCUg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54913-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54913 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.6.3, 4.7.1 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-10-12 17:02:17 UTC --- Fails with gcc version 4.8.0 20121007 (experimental) (GCC) The code should be accepted, and the diagnostic should make sense!
next prev parent reply other threads:[~2012-10-12 17:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-12 17:01 [Bug c++/54913] New: " redi at gcc dot gnu.org 2012-10-12 17:02 ` redi at gcc dot gnu.org [this message] 2012-10-12 17:13 ` [Bug c++/54913] " paolo.carlini at oracle dot com 2012-10-13 0:00 ` redi at gcc dot gnu.org 2012-10-13 13:35 ` redi at gcc dot gnu.org 2012-10-13 17:17 ` [Bug c++/54913] [4.8 Regression] qualified lookup in ctor of class template fails to find static member of reference type redi at gcc dot gnu.org 2012-10-15 9:52 ` rguenth at gcc dot gnu.org 2012-12-03 15:52 ` rguenth at gcc dot gnu.org 2012-12-06 15:30 ` jason at gcc dot gnu.org 2012-12-06 20:21 ` jason at gcc dot gnu.org 2012-12-06 20:23 ` jason 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-54913-4-jQIdkEHCUg@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).