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++/105425] [12/13 Regression] ambiguous template instantiation with hana::when
Date: Thu, 28 Apr 2022 18:07:03 +0000	[thread overview]
Message-ID: <bug-105425-4-LWaSOSH3q6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105425-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:38bdf2dccf6a239598ef808ed11a904e5f2a186e

commit r12-8317-g38bdf2dccf6a239598ef808ed11a904e5f2a186e
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Apr 28 13:10:56 2022 -0400

    c++: partial ordering and dependent operator expr [PR105425]

    Here ever since r12-6022-gbb2a7f80a98de3 we stopped deeming the partial
    specialization #2 to be more specialized than #1 ultimately because
    dependent operator expressions now have a DEPENDENT_OPERATOR_TYPE type
    instead of an empty type, and this made unify stop deducing T(2) == 1
    for K during partial ordering for #1 and #2.

    This minimal patch fixes this by making the relevant logic in unify
    treat DEPENDENT_OPERATOR_TYPE like an empty type.

            PR c++/105425

    gcc/cp/ChangeLog:

            * pt.cc (unify) <case TEMPLATE_PARM_INDEX>: Treat
            DEPENDENT_OPERATOR_TYPE like an empty type.

    gcc/testsuite/ChangeLog:

            * g++.dg/template/partial-specialization13.C: New test.

    (cherry picked from commit 509fd16da8528444dccc98cef57a18a295c3f1b4)

  parent reply	other threads:[~2022-04-28 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 15:10 [Bug c++/105425] New: " ed at catmur dot uk
2022-04-28 15:46 ` [Bug c++/105425] " mpolacek at gcc dot gnu.org
2022-04-28 15:56 ` [Bug c++/105425] [12/13 Regression] " ppalka at gcc dot gnu.org
2022-04-28 17:11 ` cvs-commit at gcc dot gnu.org
2022-04-28 18:07 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-28 18:49 ` 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-105425-4-LWaSOSH3q6@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).