This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++ Patch] Consistently use OVL_P
- From: Marek Polacek <polacek at redhat dot com>
- To: Paolo Carlini <paolo dot carlini at oracle dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Jason Merrill <jason at redhat dot com>
- Date: Tue, 14 May 2019 13:22:27 -0400
- Subject: Re: [C++ Patch] Consistently use OVL_P
- References: <660300ac-0dfb-5104-2606-cface7b37d70@oracle.com>
On Tue, May 14, 2019 at 05:28:09PM +0200, Paolo Carlini wrote:
> Hi,
>
> another straightforward one sitting in my tree... Sanity checked on
> x86_64-linux.
>
> Thanks, Paolo.
>
> ///////////////////
>
> 2019-05-14 Paolo Carlini <paolo.carlini@oracle.com>
>
> * call.c (perform_overload_resolution, build_new_method_call_1):
> Use OVL_P.
> * decl.c (grokfndecl): Likewise.
> * mangle.c (write_expression): Likewise.
> * parser.c (cp_parser_template_id): Likewise.
> * pt.c (resolve_overloaded_unification, type_dependent_expression_p):
> Likewise.
> * search.c (build_baselink): Likewise.
> * tree.c (is_overloaded_fn, dependent_name, maybe_get_fns): Likewise.
Looks fine.
OVL_P says "TEMPLATE_DECLS are always wrapped in an OVERLOAD, so we don't need
to check them", but I wouldn't mess with that in a cleanup patch like this.
Marek