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++/92918] [9/10 Regression] Does not do name lookup when using from base class
Date: Tue, 12 Apr 2022 03:57:43 +0000	[thread overview]
Message-ID: <bug-92918-4-LcEgqguTmT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92918-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:4195fced8a13422db94e179404588d9d887a036a

commit r12-8098-g4195fced8a13422db94e179404588d9d887a036a
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Apr 11 17:51:43 2022 -0400

    c++: using operator= [PR105223]

    In a template class A we normally add an implicit using A::operator= as a
    placeholder for the implicitly declared operator whose signature we don't
    know yet.  In my patch for PR92918 I stopped doing that if the class has an
    explicit operator=, but that was wrong; an operator= taking an unrelated
    type doesn't prevent the implicit declaration.

    When I was working on that patch, the change was necessary to avoid another
    regression, but apparently it is no longer needed.

            PR c++/105223
            PR c++/92918

    gcc/cp/ChangeLog:

            * class.cc (finish_struct): Always using op=.

    gcc/testsuite/ChangeLog:

            * g++.dg/template/using31.C: New test.

  parent reply	other threads:[~2022-04-12  3:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92918-4@http.gcc.gnu.org/bugzilla/>
2021-04-07 19:27 ` [Bug c++/92918] [8/9/10/11 " cvs-commit at gcc dot gnu.org
2021-04-07 19:28 ` [Bug c++/92918] [8/9/10 " jason at gcc dot gnu.org
2021-05-14  9:52 ` [Bug c++/92918] [9/10 " jakub at gcc dot gnu.org
2021-05-20 21:35 ` cvs-commit at gcc dot gnu.org
2021-06-01  8:15 ` rguenth at gcc dot gnu.org
2022-03-18 18:08 ` cvs-commit at gcc dot gnu.org
2022-04-12  3:57 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-12 13:18 ` 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-92918-4-LcEgqguTmT@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).