public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113191] [11/12/13/14 Regression] Incorrect overload resolution when base class function introduced with a using declaration is more constrained than a function declared in the derived class
Date: Thu, 11 Jan 2024 22:02:01 +0000	[thread overview]
Message-ID: <bug-113191-4-V63oZFxU6e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113191-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113191

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:61b493f17e6fea5a0fb45b6a050259ca326c13a7

commit r14-7157-g61b493f17e6fea5a0fb45b6a050259ca326c13a7
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Jan 9 05:15:01 2024 -0500

    c++: corresponding object parms [PR113191]

    As discussed, our handling of corresponding object parameters needed to
    handle the using-declaration case better.  And I took the opportunity to
    share code between the add_method and cand_parms_match uses.

    This patch specifically doesn't compare reversed parameters, but a
follow-up
    patch will.

            PR c++/113191

    gcc/cp/ChangeLog:

            * class.cc (xobj_iobj_parameters_correspond): Add context parm.
            (object_parms_correspond): Factor out of...
            (add_method): ...here.
            * method.cc (defaulted_late_check): Use it.
            * call.cc (class_of_implicit_object): New.
            (object_parms_correspond): Overload taking two candidates.
            (cand_parms_match): Use it.
            (joust): Check reversed before comparing constraints.
            * cp-tree.h (object_parms_correspond): Declare.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-memfun4.C: New test.

  parent reply	other threads:[~2024-01-11 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 17:00 [Bug c++/113191] New: [10.1/11/12/13/14 " waffl3x at protonmail dot com
2024-01-02 15:49 ` [Bug c++/113191] [11/12/13/14 " ppalka at gcc dot gnu.org
2024-01-02 18:24 ` waffl3x at protonmail dot com
2024-01-11 22:02 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-12 15:14 ` jason at gcc dot gnu.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=bug-113191-4-V63oZFxU6e@http.gcc.gnu.org/bugzilla/ \
    --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).