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++/107303] [13 Regression] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3060 with nested __builtin_shufflevector() since r13-2978-g43faf3e5445b5717
Date: Tue, 24 Jan 2023 03:26:33 +0000	[thread overview]
Message-ID: <bug-107303-4-oXFAfg2VWZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107303-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:049a52909075117f5112971cc83952af2a818bc1

commit r13-5318-g049a52909075117f5112971cc83952af2a818bc1
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Jan 23 16:25:07 2023 -0500

    c++: TARGET_EXPR collapsing [PR107303]

    In r13-2978 I tried to eliminate TARGET_EXPR around TARGET_EXPR by
    discarding the outer one, but as in this testcase that breaks if the
    TARGET_EXPR_SLOT of the outer one is used elsewhere.  But it should always
    be safe to strip the inner one; if its slot were reused, there would be a
    COMPOUND_EXPR around the TARGET_EXPR.

    For 107329, if we're setting *walk_subtrees, we also need to fold
    TARGET_EXPR_CLEANUP.

            PR c++/107303
            PR c++/107329

    gcc/cp/ChangeLog:

            * cp-gimplify.cc (cp_fold_r) [TARGET_EXPR]: In case of double
            TARGET_EXPR, keep the outer one instead of the inner one.
            (maybe_replace_decl): New.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/builtin-shufflevector-5.C: New test.
            * g++.dg/init/new51.C: New test.

  parent reply	other threads:[~2023-01-24  3:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 11:26 [Bug c++/107303] New: [13 Regression] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3060 with nested __builtin_shufflevector() zsojka at seznam dot cz
2022-10-18 11:40 ` [Bug c++/107303] [13 Regression] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3060 with nested __builtin_shufflevector() since r13-2978-g43faf3e5445b5717 marxin at gcc dot gnu.org
2022-10-18 12:44 ` jakub at gcc dot gnu.org
2022-10-18 12:46 ` jakub at gcc dot gnu.org
2022-10-18 12:46 ` jakub at gcc dot gnu.org
2023-01-23 21:16 ` jason at gcc dot gnu.org
2023-01-24  3:26 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-24  3:26 ` 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-107303-4-oXFAfg2VWZ@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).