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++/105637] [12 Regression] Wrong overload selected in base class
Date: Thu, 21 Jul 2022 16:48:08 +0000	[thread overview]
Message-ID: <bug-105637-4-LSnBnOdnf7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105637-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:41487bff13fa98607ab5548bc1a0dca71147a5ac

commit r12-8603-g41487bff13fa98607ab5548bc1a0dca71147a5ac
Author: Patrick Palka <ppalka@redhat.com>
Date:   Fri Jun 3 12:06:59 2022 -0400

    c++: cv-quals of dummy obj for non-dep memfn call [PR105637]

    In non-dependent23.C below we expect the Base::foo calls to
    resolve to the second, third and fourth overloads respectively in light
    of the cv-qualifiers of 'this' in each case.  But ever since
    r12-6075-g2decd2cabe5a4f, the calls incorrectly resolve to the first
    overload at instantiation time.

    This happens because the calls to Base::foo are all deemed
    non-dependent (ever since r7-755-g23cb72663051cd made us ignore 'this'
    dependence when considering the dependence of a non-static memfn call),
    hence we end up checking the call ahead of time, using as the object
    argument a dummy object of type Base.  Since this object argument is
    cv-unqualified, the calls in turn resolve to the unqualified overload
    of baseDevice.  Before r12-6075 this incorrect result would just get
    silently discarded and we'd end up redoing OR at instantiation time
    using 'this' as the object argument.  But after r12-6075 we now reuse
    this incorrect result at instantiation time.

    This patch fixes this by making maybe_dummy_object respect the cv-quals
    of (the non-lambda) 'this' when returning a dummy object.  Thus, ahead
    of time OR using a dummy object will give us the right answer that's
    consistent with the instantiation time answer.

    An earlier version of this patch didn't handle 'this'-capturing lambdas
    correctly, which broke lambda-this22.C below.

            PR c++/105637

    gcc/cp/ChangeLog:

            * tree.cc (maybe_dummy_object): When returning a dummy
            object, respect the cv-quals of 'this' if available.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/lambda/lambda-this22.C: New test.
            * g++.dg/template/non-dependent23.C: New test.

    (cherry picked from commit 44a5bd6d933d86ed988fc4695aa00f122cf83eb4)

  parent reply	other threads:[~2022-07-21 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 20:40 [Bug c++/105637] New: [11 " ted at lyncon dot se
2022-05-17 20:55 ` [Bug c++/105637] [12/13 " ppalka at gcc dot gnu.org
2022-05-18  2:38 ` john.robert.lefebvre at gmail dot com
2022-05-18 12:39 ` rguenth at gcc dot gnu.org
2022-06-03 16:07 ` cvs-commit at gcc dot gnu.org
2022-06-03 16:08 ` [Bug c++/105637] [12 " ppalka at gcc dot gnu.org
2022-06-03 16:09 ` ted at lyncon dot se
2022-06-03 16:17 ` john.robert.lefebvre at gmail dot com
2022-07-21 16:48 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-21 16:50 ` 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-105637-4-LSnBnOdnf7@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).