public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11752] partial ordering overloaded function templates Date: Tue, 05 Aug 2003 16:33:00 -0000 [thread overview] Message-ID: <20030805163259.9387.qmail@sources.redhat.com> (raw) In-Reply-To: <20030731184837.11752.nbecker@fred.net> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11752 ------- Additional Comments From bangerth at dealii dot org 2003-08-05 16:32 ------- Here's a self-contained testcase: ----------------------------- template <typename> struct X {}; template<int shift, typename T> T f (T); template<int shift, typename T> X<T> f (X<T>); int main () { X<int> x; f<6> (x); } ------------------------------ It fails with 3.4 and icc7: g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c bug.cc bug.cc: In function `int main()': bug.cc:8: error: call of overloaded `f(X<int>&)' is ambiguous bug.cc:3: note: candidates are: T f(T) [with int shift = 6, T = X<int>] bug.cc:4: note: X<T> f(X<T>) [with int shift = 6, T = int] g/x> g/x> icc -c bug.cc bug.cc(8): error: more than one instance of overloaded function "f" matches the argument list: function template "f<shift,T>(T)" function template "f<shift,T>(X<T>)" argument types are: (X<int>) f<6> (x); ^ compilation aborted for bug.cc (code 2) I recall that we had another PR like this, where the existence of the first template arg made a difference, and I remember I didn't understand the reasoning why that was deemed illegal. Note that if the int template arg is removed (along with the <6> on the call of f), then both compilers grok the code. Someone with more knowledge will have to look at this. W.
next prev parent reply other threads:[~2003-08-05 16:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-31 18:48 [Bug c++/11752] New: " nbecker at fred dot net 2003-07-31 19:08 ` [Bug c++/11752] " pinskia at physics dot uc dot edu 2003-07-31 19:16 ` nbecker at hns dot com 2003-08-04 14:54 ` nbecker at fred dot net 2003-08-04 14:58 ` pinskia at physics dot uc dot edu 2003-08-04 14:58 ` pinskia at physics dot uc dot edu 2003-08-04 19:44 ` pinskia at physics dot uc dot edu 2003-08-05 16:29 ` lerdsuwa at gcc dot gnu dot org 2003-08-05 16:33 ` bangerth at dealii dot org [this message] 2003-08-05 16:50 ` nbecker at hns 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=20030805163259.9387.qmail@sources.redhat.com \ --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).