public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dodji at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/47957] [4.3/4.4/4.5/4.6 Regression] Type mismatch when a class derived a same name with template parameter Date: Mon, 07 Mar 2011 16:26:00 -0000 [thread overview] Message-ID: <bug-47957-4-GVcqQV5Z5a@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47957-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47957 Dodji Seketeli <dodji at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|unassigned at gcc dot |dodji at gcc dot gnu.org |gnu.org | --- Comment #5 from Dodji Seketeli <dodji at gcc dot gnu.org> 2011-03-07 16:26:23 UTC --- Here is a testcase that does away with #include <iostream> and #include <typeid> requirements: struct S { int m; S() : m(0) { } }; struct Base { typedef S T; }; template<class T> struct Derived : public Base { int foo() { T a; // This is Base::T, not the template parameter. return a.m; } }; int main() { Derived<char> d; return d.foo(); }
next prev parent reply other threads:[~2011-03-07 16:26 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-02 16:06 [Bug c++/47957] New: " boostcpp at gmail dot com 2011-03-02 16:13 ` [Bug c++/47957] [4.3/4.4/4.5/4.6 Regression] " rguenth at gcc dot gnu.org 2011-03-02 18:21 ` jakub at gcc dot gnu.org 2011-03-03 11:20 ` jakub at gcc dot gnu.org 2011-03-03 23:43 ` jason at gcc dot gnu.org 2011-03-04 16:01 ` dodji at gcc dot gnu.org 2011-03-07 16:26 ` dodji at gcc dot gnu.org [this message] 2011-03-08 15:38 ` dodji at gcc dot gnu.org 2011-03-08 15:41 ` [Bug c++/47957] [4.3/4.4/4.5 " jakub at gcc dot gnu.org 2011-03-08 21:14 ` dodji at gcc dot gnu.org 2011-03-08 22:20 ` dodji at gcc dot gnu.org 2011-03-08 22:30 ` [Bug c++/47957] [4.3 " dodji at gcc dot gnu.org 2011-06-27 12:15 ` rguenth 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-47957-4-GVcqQV5Z5a@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).