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++/81311] [7 Regression] An std::ref argument calls copy constructor instead of template constructor in C++17 mode Date: Fri, 13 May 2022 23:46:44 +0000 [thread overview] Message-ID: <bug-81311-4-3IP8M4xPLF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-81311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81311 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:62ecd2b8d46aaf96caef5fa78953216629e49ebd commit r13-460-g62ecd2b8d46aaf96caef5fa78953216629e49ebd Author: Marek Polacek <polacek@redhat.com> Date: Fri May 13 19:45:03 2022 -0400 c++: Add fixed test [PR81952] This was fixed by r258755: PR c++/81311 - wrong C++17 overload resolution. PR c++/81952 gcc/testsuite/ChangeLog: * g++.dg/overload/conv-op4.C: New test.
prev parent reply other threads:[~2022-05-13 23:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-81311-4@http.gcc.gnu.org/bugzilla/> 2021-08-17 7:01 ` pinskia at gcc dot gnu.org 2022-05-13 23:46 ` cvs-commit at gcc dot gnu.org [this message]
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-81311-4-3IP8M4xPLF@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: linkBe 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).