public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "benko at sztaki dot hu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11828] New: [3.4 regression] qualified dependent name looked up too early Date: Wed, 06 Aug 2003 09:18:00 -0000 [thread overview] Message-ID: <20030806091852.11828.benko@sztaki.hu> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11828 Summary: [3.4 regression] qualified dependent name looked up too early Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: benko at sztaki dot hu CC: gcc-bugs at gcc dot gnu dot org hydra:~/c/proba$ cat templ_overload.cc namespace n { template <typename T> void f(T a) { a.f(); } template <typename T> void g(T a) { n::f(a); } } struct s {}; namespace n { void f(s) {} } int main() { n::g(s()); return 0; } hydra:~/c/proba$ g++-cvs templ_overload.cc templ_overload.cc: In function `void n::f(T) [with T = s]': templ_overload.cc:14: instantiated from `void n::g(T) [with T = s]' templ_overload.cc:31: instantiated from here templ_overload.cc:7: error: 'struct s' has no member named 'f' zsh: exit 1 g++-cvs templ_overload.cc hydra:~/c/proba$ g++-cvs -v Reading specs from /gml/shared/gcc-cvs/lib/gcc/i686-pc-linux-gnu/3.4/specs Configured with: ../gcc/configure --prefix=/gml/shared/gcc-cvs --enable-languages=c++ Thread model: posix gcc version 3.4 20030806 (experimental) hydra:~/c/proba$ g++3 templ_overload.cc hydra:~/c/proba$ g++3 -v Reading specs from /gml/shared/gcc-3.3/lib/gcc-lib/i686-pc-linux-gnu/3.3/specs Configured with: ../gcc-3.3/configure --prefix=/gml/shared/gcc-3.3 Thread model: posix gcc version 3.3 hydra:~/c/proba$ workarounds: 1. unqualify f in the definition of g. I cannot do this, because in real life n=std, f=iter_swap, g=reverse. 2. Move the definition of the overload for f before the definition of g.
next reply other threads:[~2003-08-06 9:18 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-06 9:18 benko at sztaki dot hu [this message] 2003-08-06 14:39 ` [Bug c++/11828] " bangerth at dealii dot org 2003-08-07 7:06 ` benko at sztaki dot hu 2003-08-07 13:20 ` bangerth at dealii dot org 2003-08-07 13:21 ` bangerth at dealii dot org 2003-08-11 7:04 ` benko at sztaki dot hu 2003-08-11 21:00 ` janis187 at us dot ibm dot com 2003-08-21 6:02 ` mmitchel at gcc dot gnu dot org 2004-04-26 12:57 ` pinskia at gcc dot gnu dot org 2004-05-11 18:34 ` jason at gcc dot gnu dot org 2004-05-11 18:38 ` jason at gcc dot gnu dot org 2004-05-11 18:53 ` [Bug c++/11828] [3.4/3.5 " pinskia at gcc dot gnu dot org 2004-05-11 18:56 ` pinskia at gcc dot gnu dot org 2004-05-11 19:23 ` bangerth at dealii dot org 2004-05-11 19:24 ` jason at redhat dot com 2004-05-11 19:37 ` bangerth at dealii dot org 2004-06-03 22:29 ` pinskia at gcc dot gnu dot org 2004-06-10 20:04 ` jason at gcc dot gnu dot org 2004-10-28 13:53 ` [Bug c++/11828] [3.4/4.0 " pinskia at gcc dot gnu dot org 2005-02-21 19:12 ` smcpeak at cs dot berkeley dot edu 2005-03-03 22:55 ` pinskia at gcc dot gnu dot org 2005-03-04 5:00 ` smcpeak at cs dot berkeley dot edu
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=20030806091852.11828.benko@sztaki.hu \ --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).