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++/103783] Ambiguous overload between constrained static member and unconstrained non-static member Date: Mon, 10 Jan 2022 21:16:40 +0000 [thread overview] Message-ID: <bug-103783-4-Vd9hcj2Iqn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103783-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103783 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:1e4a9f22ac21da012fc93198a22e30b70e8fdf84 commit r11-9450-g1e4a9f22ac21da012fc93198a22e30b70e8fdf84 Author: Patrick Palka <ppalka@redhat.com> Date: Mon Jan 10 14:57:51 2022 -0500 c++: "more constrained" vs staticness of memfn [PR103783] Here we're rejecting the calls to g1 and g2 as ambiguous even though one overload is more constrained than the other (and they're otherwise tied), because the implicit 'this' parameter of the non-static overload causes cand_parms_match to think the function parameter lists aren't equivalent. This patch fixes this by making cand_parms_match skip over 'this' appropriately. Note that this bug only affects partial ordering of non-template member functions because for member function templates more_specialized_fn seems to already skip over 'this' appropriately. PR c++/103783 gcc/cp/ChangeLog: * call.c (cand_parms_match): Skip over 'this' when given one static and one non-static member function. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-memfun2.C: New test. (cherry picked from commit 3e95a974c39e922d19bf7ac1246730c516ae01f2)
next prev parent reply other threads:[~2022-01-10 21:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-21 1:39 [Bug c++/103783] New: " barry.revzin at gmail dot com 2021-12-21 1:50 ` [Bug c++/103783] " pinskia at gcc dot gnu.org 2022-01-02 5:40 ` fchelnokov at gmail dot com 2022-01-02 16:57 ` davidfromonline at gmail dot com 2022-01-02 19:23 ` davidfromonline at gmail dot com 2022-01-04 18:08 ` ppalka at gcc dot gnu.org 2022-01-10 19:59 ` cvs-commit at gcc dot gnu.org 2022-01-10 21:16 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-10 21:17 ` ppalka 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-103783-4-Vd9hcj2Iqn@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: linkBe 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).