From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Mark Mitchell <mark@codesourcery.com>
Subject: Re: [C++ Patch] Fix PR 35112
Date: Fri, 27 Nov 2009 10:05:00 -0000 [thread overview]
Message-ID: <206fcf960911270159o10e25670gf787ab686eb906@mail.gmail.com> (raw)
In-Reply-To: <4B0F9BDF.60806@oracle.com>
On Fri, Nov 27, 2009 at 3:29 AM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> Hi again,
>> Don't pretend I'm that difficult :-)
>>
>> Seriously, here is what I meant: in the current print_candidates
>> the inner for loop i(the one that goes over functions in an
>> overload set) s repeated twice. So, you can make
>> that a function of its own, say print_overloaded_functions.
>> Then print_candidates calls print_overloaded_functions in
>> the is_overloaded_fn branch, but loops over the list
>> of overload set in the else branch, calling print_overloaded_functions
>> with the TREE_VALUE. Does that make sense to you?
>>
> Sure. The below is what I have tested on x86_64-linux. Is it ok?
OK! Thanks.
Just for my curiosity, was the test for TREE_LIST in print_overloaded_functions
necessary? For which case?
-- Gaby
next prev parent reply other threads:[~2009-11-27 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 1:38 Paolo Carlini
2009-11-27 1:44 ` Gabriel Dos Reis
2009-11-27 2:29 ` Paolo Carlini
2009-11-27 2:42 ` Gabriel Dos Reis
2009-11-27 9:39 ` Paolo Carlini
2009-11-27 10:05 ` Gabriel Dos Reis [this message]
2009-11-27 10:37 ` Paolo Carlini
2009-11-27 11:54 ` Gabriel Dos Reis
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=206fcf960911270159o10e25670gf787ab686eb906@mail.gmail.com \
--to=gdr@integrable-solutions.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=paolo.carlini@oracle.com \
/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).