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++/107267] [13 Regression] ICE in cp_gimplify_init_expr, at cp/cp-gimplify.cc:253 since r13-3175-g6ffbf87ca66f4ed9 Date: Mon, 23 Jan 2023 23:35:20 +0000 [thread overview] Message-ID: <bug-107267-4-Rv8nBADVDy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107267-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107267 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:4cbc71691e47b1ca6b64feb0af678606705d2f92 commit r13-5316-g4cbc71691e47b1ca6b64feb0af678606705d2f92 Author: Jason Merrill <jason@redhat.com> Date: Mon Jan 23 17:14:11 2023 -0500 c++: TARGET_EXPR_ELIDING_P and std::move [PR107267] With -ffold-simple-inlines, we turn calls to std::move into the static_cast equivalent. In this testcase, this exposes the FindResult temporary to copy elision which is not specified by the standard, through an optimization in gimplify_modify_expr_rhs. Since the type is not TREE_ADDRESSABLE, this is not detectable by the user, so we just need to soften the assert. PR c++/107267 gcc/cp/ChangeLog: * cp-gimplify.cc (cp_gimplify_init_expr): Allow unexpected elision of trivial types. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/move2.C: New test.
next prev parent reply other threads:[~2023-01-23 23:35 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-14 16:18 [Bug c++/107267] New: ice in cp_gimplify_init_expr, at cp/cp-gimplify.cc:253 dcb314 at hotmail dot com 2022-10-14 16:25 ` [Bug c++/107267] " dcb314 at hotmail dot com 2022-10-14 16:29 ` dcb314 at hotmail dot com 2022-10-15 11:00 ` dcb314 at hotmail dot com 2022-10-16 6:39 ` dcb314 at hotmail dot com 2022-10-16 7:03 ` dcb314 at hotmail dot com 2022-10-16 7:21 ` dcb314 at hotmail dot com 2022-10-16 7:30 ` dcb314 at hotmail dot com 2022-10-17 11:31 ` [Bug c++/107267] [13 Regression] ICE in cp_gimplify_init_expr, at cp/cp-gimplify.cc:253 since r13-3175-g6ffbf87ca66f4ed9 marxin at gcc dot gnu.org 2022-10-17 11:32 ` marxin at gcc dot gnu.org 2022-10-17 11:35 ` marxin at gcc dot gnu.org 2022-10-17 11:35 ` marxin at gcc dot gnu.org 2022-10-20 18:39 ` dcb314 at hotmail dot com 2022-10-20 18:52 ` ppalka at gcc dot gnu.org 2023-01-23 22:04 ` jason at gcc dot gnu.org 2023-01-23 23:35 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-24 2:53 ` 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-107267-4-Rv8nBADVDy@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).