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++/107085] __reference_constructs_from_temporary does not detect static up-cast Date: Fri, 07 Oct 2022 22:06:20 +0000 [thread overview] Message-ID: <bug-107085-4-RiVGNaieG9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107085-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107085 --- Comment #11 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:895dd027d5dda51a95d242aec8a49a6dfa5db58d commit r13-3173-g895dd027d5dda51a95d242aec8a49a6dfa5db58d Author: Marek Polacek <polacek@redhat.com> Date: Wed Oct 5 15:51:30 2022 -0400 c++: fixes for derived-to-base reference binding [PR107085] This PR reports that struct Base {}; struct Derived : Base {}; static_assert(__reference_constructs_from_temporary(Base const&, Derived)); doesn't pass, which it should: it's just like const Base& b(Derived{}); where we bind 'b' to the Base subobject of a temporary object of type Derived. The ck_base conversion didn't have ->need_temporary_p set because we didn't need to create a temporary object just for the base, but the whole object is a temporary so we're still binding to a temporary. Since the Base subobject is an xvalue, a new function is introduced. PR c++/107085 gcc/cp/ChangeLog: * call.cc (conv_binds_ref_to_temporary): New. (ref_conv_binds_directly): Rename to... (ref_conv_binds_to_temporary): ...this. Use conv_binds_ref_to_temporary. * cp-tree.h (ref_conv_binds_directly): Rename to... (ref_conv_binds_to_temporary): ...this. * method.cc (ref_xes_from_temporary): Use ref_conv_binds_to_temporary. * parser.cc (warn_for_range_copy): Likewise. gcc/testsuite/ChangeLog: * g++.dg/ext/reference_constructs_from_temporary1.C: Adjust expected result. * g++.dg/ext/reference_converts_from_temporary1.C: Likewise. * g++.dg/cpp0x/elision4.C: New test.
next prev parent reply other threads:[~2022-10-07 22:06 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-29 10:30 [Bug c++/107085] New: " roi.jacobson1 at gmail dot com 2022-09-29 10:42 ` [Bug c++/107085] " redi at gcc dot gnu.org 2022-09-29 10:46 ` redi at gcc dot gnu.org 2022-09-29 11:11 ` roi.jacobson1 at gmail dot com 2022-09-29 11:52 ` redi at gcc dot gnu.org 2022-09-29 12:45 ` mpolacek at gcc dot gnu.org 2022-10-04 19:34 ` mpolacek at gcc dot gnu.org 2022-10-04 20:41 ` mpolacek at gcc dot gnu.org 2022-10-05 6:43 ` redi at gcc dot gnu.org 2022-10-05 15:29 ` mpolacek at gcc dot gnu.org 2022-10-05 16:07 ` mpolacek at gcc dot gnu.org 2022-10-07 22:06 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-07 22:06 ` mpolacek 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-107085-4-RiVGNaieG9@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).