From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 690 invoked by alias); 21 Feb 2013 19:34:37 -0000 Received: (qmail 618 invoked by uid 22791); 21 Feb 2013 19:34:36 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 Feb 2013 19:34:31 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r1LJYVOj001287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 21 Feb 2013 14:34:31 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r1LJYUPM013434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 21 Feb 2013 14:34:30 -0500 From: Tom Tromey To: gdb-patches@sourceware.org Subject: Re: RFC: fix PR c++/15116 References: <87ppztbh2x.fsf@fleche.redhat.com> Date: Thu, 21 Feb 2013 19:34:00 -0000 In-Reply-To: <87ppztbh2x.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 21 Feb 2013 12:30:14 -0700") Message-ID: <87liahbgvu.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2013-02/txt/msg00568.txt.bz2 >>>>> "Tom" == Tom Tromey writes: Tom> Second, overload resolution can actually do a kind of second overload Tom> resolution, according to the standard. This is well-formed: Tom> int f(int x) { return x; } Tom> double f(double x) { return x; } A minor note. It turns out that the example as written actually does work. This is because the correct "f" appears first in the CU. If you swap these two lines, you can make it fail: (gdb) p overload(0,f) Cannot resolve function overload to any overloaded instance I've pointed this out in the PR I'm filing. Tom