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++/101698] [9/10/11/12 Regression] Template type conversion operator from base class preferred over matching overload
Date: Thu, 14 Apr 2022 00:24:37 +0000	[thread overview]
Message-ID: <bug-101698-4-aLlRtVtv48@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101698-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:d4e00ccef6c706a4a4a6446bffaf4111f98d5771

commit r12-8151-gd4e00ccef6c706a4a4a6446bffaf4111f98d5771
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Apr 13 14:49:04 2022 -0400

    c++: template conversion op [PR101698]

    Asking for conversion to a dependent type also makes a BASELINK dependent.

            PR c++/101698

    gcc/cp/ChangeLog:

            * pt.cc (tsubst_baselink): Also check dependent optype.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2022-04-14  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 19:11 [Bug c++/101698] New: " ammiera at hotmail dot com
2021-08-02  8:28 ` [Bug c++/101698] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org
2021-08-02  9:37 ` redi at gcc dot gnu.org
2021-08-02 10:10 ` redi at gcc dot gnu.org
2022-01-17 13:58 ` rguenth at gcc dot gnu.org
2022-04-14  0:24 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-14  0:26 ` [Bug c++/101698] [9/10/11 " jason at gcc dot gnu.org
2022-05-13 16:28 ` cvs-commit at gcc dot gnu.org
2022-05-13 17:14 ` [Bug c++/101698] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-13 17:41 ` [Bug c++/101698] [9 " cvs-commit at gcc dot gnu.org
2022-05-13 17:58 ` 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-101698-4-aLlRtVtv48@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).