public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19203] [3.4/4.0/4.1 Regression] Partial ordering failure between function reference and generic const reference
Date: Thu, 31 Mar 2005 17:37:00 -0000 [thread overview]
Message-ID: <20050331173637.12674.qmail@sourceware.org> (raw)
In-Reply-To: <20041230121859.19203.giovannibajo@libero.it>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-03-31 17:36 -------
Subject: Bug 19203
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: nathan@gcc.gnu.org 2005-03-31 17:36:18
Modified files:
gcc/cp : ChangeLog call.c cp-tree.h pt.c
gcc/testsuite : ChangeLog
gcc/testsuite/g++.dg/parse: ambig3.C
Added files:
gcc/testsuite/g++.dg/template: spec20.C spec21.C
Log message:
cp:
PR c++/19203, implement DR 214
* call.c (joust): Use more_specialized_fn.
* cp-tree.h (DEDUCE_ORDER): Remove.
(more_specialized): Replace with ...
(more_specialized_fn): ... this.
* pt.c (maybe_adjust_types_for_deduction): Remove DEDUCE_ORDER
case.
(type_unification_real): Remove DEDUCE_ORDER case.
(more_specialized): Replace with ...
(more_specialized_fn): ... this. Implement DR 214.
(most_specialized_instantiation): Use get_bindings_real directly.
testsuite:
PR c++/19203, DR 214
* g++.dg/parse/ambig3.C: Not ambiguous.
* g++.dg/template/spec20.C: New.
* g++.dg/template/spec21.C: New.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.4681&r2=1.4682
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/call.c.diff?cvsroot=gcc&r1=1.532&r2=1.533
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/cp-tree.h.diff?cvsroot=gcc&r1=1.1114&r2=1.1115
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/pt.c.diff?cvsroot=gcc&r1=1.986&r2=1.987
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.5245&r2=1.5246
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/parse/ambig3.C.diff?cvsroot=gcc&r1=1.1&r2=1.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/template/spec20.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/template/spec21.C.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19203
next prev parent reply other threads:[~2005-03-31 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 12:19 [Bug c++/19203] New: " giovannibajo at libero dot it
2004-12-30 12:19 ` [Bug c++/19203] " giovannibajo at libero dot it
2004-12-30 12:20 ` giovannibajo at libero dot it
2004-12-30 14:29 ` [Bug c++/19203] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-27 5:45 ` pinskia at gcc dot gnu dot org
2005-03-24 19:05 ` [Bug c++/19203] [3.4/4.0/4.1 " nathan at gcc dot gnu dot org
2005-03-30 13:10 ` nathan at gcc dot gnu dot org
2005-03-31 17:37 ` cvs-commit at gcc dot gnu dot org [this message]
2005-03-31 17:47 ` nathan at gcc dot gnu dot org
2005-03-31 18:04 ` mmitchel at gcc dot gnu dot org
2005-04-04 9:49 ` [Bug c++/19203] [3.4/4.0 " nathan at gcc dot gnu dot org
2005-04-07 7:25 ` [Bug c++/19203] [3.4/4.0 Regression] [DR 214] " igodard at pacbell dot net
2005-05-10 13:30 ` nathan at gcc dot gnu dot org
2005-05-10 13:48 ` cvs-commit at gcc dot gnu dot org
2005-06-21 20:59 ` bangerth at dealii 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=20050331173637.12674.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: link
Be 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).