public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/25855] template specialisation not always found (partial ordering) Date: Thu, 19 Jan 2006 14:43:00 -0000 [thread overview] Message-ID: <20060119144344.10522.qmail@sourceware.org> (raw) In-Reply-To: <bug-25855-3563@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from nathan at gcc dot gnu dot org 2006-01-19 14:43 ------- comment #10 is incorrect. Regardless of the validity/invalidity of the code, the fact that comment#4 shows us producing different code depending on the ordering of the template decls indicates a bug. (I also fail to see the relevancy of DR214, as there are no undeduceable template parameters, nor any reference arguments.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25855
next prev parent reply other threads:[~2006-01-19 14:43 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-19 11:11 [Bug c++/25855] New: template specialisation not always found mueller at kde dot org 2006-01-19 11:12 ` [Bug c++/25855] " mueller at kde dot org 2006-01-19 11:13 ` mueller at kde dot org 2006-01-19 13:09 ` rguenth at gcc dot gnu dot org 2006-01-19 13:15 ` rguenth at gcc dot gnu dot org 2006-01-19 13:36 ` [Bug c++/25855] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-01-19 13:42 ` pinskia at gcc dot gnu dot org 2006-01-19 13:53 ` [Bug c++/25855] template specialisation not always found (partial ordering) pinskia at gcc dot gnu dot org 2006-01-19 14:13 ` pinskia at gcc dot gnu dot org 2006-01-19 14:22 ` nathan at gcc dot gnu dot org 2006-01-19 14:29 ` pinskia at gcc dot gnu dot org 2006-01-19 14:43 ` nathan at gcc dot gnu dot org [this message] 2006-01-21 1:24 ` janis at gcc dot gnu dot org 2006-01-23 16:27 ` [Bug c++/25855] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-01-25 6:30 ` mmitchel at gcc dot gnu dot org 2006-01-28 3:27 ` mmitchel at gcc dot gnu dot org 2006-01-28 4:13 ` mmitchel at gcc dot gnu dot org 2006-01-28 19:24 ` mmitchel at gcc dot gnu dot org 2006-01-28 19:24 ` mmitchel at gcc dot gnu dot org 2006-01-28 19:25 ` mmitchel at gcc dot gnu dot org 2006-01-28 19:28 ` mmitchel at gcc dot gnu dot org 2006-01-28 19:37 ` mmitchel at gcc dot gnu dot 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=20060119144344.10522.qmail@sourceware.org \ --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).