public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/3614: failing overloading of template member functions in template classes Date: Thu, 21 Nov 2002 19:06:00 -0000 [thread overview] Message-ID: <20021116020604.15787.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/3614; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/3614: failing overloading of template member functions in template classes Date: Fri, 15 Nov 2002 20:10:17 -0600 (CST) May be related to PR 509. The problem also got worse. With 3.3 CVS from 2002-11-10, I get x.cc:15: error: redefinition of `int A<N>::f()' x.cc:12: error: `int A<N>::f()' previously declared here x.cc:15: error: no `int A<N>::f()' member function declared in class `A<N>' x.cc:15: error: expected 2 levels of template parms for `int A<N>::f()', got 1 x.cc: In instantiation of `A<42>': x.cc:19: instantiated from here x.cc:7: internal compiler error: in retrieve_specialization, at cp/pt.c:727 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. Also, the circular error messages are not very helpful (redefinition -- not existing -- but expecting something from it; no what?) W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-16 2:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-21 19:06 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-08-12 4:04 gdr 2001-07-09 2:56 sts
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=20021116020604.15787.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=gdr@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).