public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53405] [4.5/4.6 Regression] Enum-dependent class template instantiations not recognized Date: Sat, 26 May 2012 23:54:00 -0000 [thread overview] Message-ID: <bug-53405-4-EB3JCZgTvk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53405-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53405 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid Known to work| |4.4.6, 4.7.0, 4.8.0 Target Milestone|--- |4.5.4 Summary|Enum-dependent class |[4.5/4.6 Regression] |template instantiations not |Enum-dependent class |recognized |template instantiations not | |recognized Known to fail| |4.5.4, 4.6.0
next prev parent reply other threads:[~2012-05-26 23:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-18 17:37 [Bug c++/53405] New: " ibugs at qult dot net 2012-05-18 19:49 ` [Bug c++/53405] " daniel.kruegler at googlemail dot com 2012-05-26 23:54 ` pinskia at gcc dot gnu.org [this message] 2012-05-28 16:21 ` [Bug c++/53405] [4.5/4.6 Regression] " paolo.carlini at oracle dot com
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-53405-4-EB3JCZgTvk@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).