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++/100963] [11/12 Regression] GCC 11 regression: templated constructor with std::initializer_list<T> is not selected
Date: Tue, 08 Jun 2021 17:29:09 +0000	[thread overview]
Message-ID: <bug-100963-4-JRscRE2s2p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100963-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:5af06ce836d4d8d1654db3855db8b86a994faf49

commit r11-8526-g5af06ce836d4d8d1654db3855db8b86a994faf49
Author: Jason Merrill <jason@redhat.com>
Date:   Tue Jun 8 09:19:58 2021 -0400

    c++: braced-list overload resolution [PR100963]

    My PR969626 patch made us ignore template candidates when there's a perfect
    non-template candidate.  In this case, we were considering B(int) a perfect
    match for B({0}), but the brace elision makes it imperfect.

            PR c++/100963

    gcc/cp/ChangeLog:

            * call.c (perfect_conversion_p): Check check_narrowing.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/initlist124.C: New test.

  parent reply	other threads:[~2021-06-08 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 11:06 [Bug c++/100963] New: " j.l.k at gmx dot com
2021-06-08 11:12 ` [Bug c++/100963] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-06-08 11:15 ` j.l.k at gmx dot com
2021-06-08 12:39 ` ppalka at gcc dot gnu.org
2021-06-08 13:11 ` jason at gcc dot gnu.org
2021-06-08 17:28 ` cvs-commit at gcc dot gnu.org
2021-06-08 17:29 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-08 17:35 ` 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-100963-4-JRscRE2s2p@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).