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 tree-optimization/105528] [11/12/13 Regression] ICE: in expand_expr_real_2, at expr.cc:10290 with -O2 -mavx512f since r11-8059-g5240c5ca2e2b1f36
Date: Tue, 10 May 2022 16:42:07 +0000	[thread overview]
Message-ID: <bug-105528-4-J6IoCtxFrB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105528-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:9468cc35daca9fd6a0ec479217bb40a77616fb25

commit r12-8362-g9468cc35daca9fd6a0ec479217bb40a77616fb25
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 10 18:34:08 2022 +0200

    isel: Fix up gimple_expand_vec_set_expr [PR105528]

    The following testcase ICEs (and only without -g), because we don't replace
    one VEC_COND_EXPR with .VCOND* call.
    We don't do that because gimple_expand_vec_set_expr adds some stmts before
    *gsi and then uses gsi_remove to remove it.  gsi_remove moves the iterator
    to the next stmt and in the caller we then do gsi_next before looking at
    another stmt, which means we can skip processing of one stmt, which in this
    case happened to be a VEC_COND_EXPR but with -g is some debug stmt in
    between.  As we always emit some stmts before it, it is easy to update the
    iterator to the last stmt emitted there, so that caller continues really
    with the next stmt.

    2022-05-10  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/105528
            * gimple-isel.cc (gimple_expand_vec_set_expr): After gsi_remove
            set *gsi to gsi_for_stmt (ass_stmt).  Fix up function comment.

            * gcc.dg/pr105528.c: New test.

    (cherry picked from commit ddd46293e2b508b260eefe1adbad6720df7a5dd2)

  parent reply	other threads:[~2022-05-10 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  6:29 [Bug rtl-optimization/105528] New: [11/12/13 Regression] ICE: in expand_expr_real_2, at expr.cc:10290 with -O2 -mavx512f zsojka at seznam dot cz
2022-05-09  6:36 ` [Bug target/105528] " pinskia at gcc dot gnu.org
2022-05-09  6:39 ` [Bug tree-optimization/105528] " pinskia at gcc dot gnu.org
2022-05-09  6:41 ` pinskia at gcc dot gnu.org
2022-05-09  6:43 ` pinskia at gcc dot gnu.org
2022-05-09  7:03 ` [Bug tree-optimization/105528] [11/12/13 Regression] ICE: in expand_expr_real_2, at expr.cc:10290 with -O2 -mavx512f since r11-8059-g5240c5ca2e2b1f36 marxin at gcc dot gnu.org
2022-05-09  7:52 ` jakub at gcc dot gnu.org
2022-05-09  8:14 ` rguenth at gcc dot gnu.org
2022-05-09  9:58 ` jakub at gcc dot gnu.org
2022-05-09 10:16 ` pinskia at gcc dot gnu.org
2022-05-10 16:34 ` cvs-commit at gcc dot gnu.org
2022-05-10 16:42 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-10 16:47 ` cvs-commit at gcc dot gnu.org
2022-05-10 16:49 ` jakub 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-105528-4-J6IoCtxFrB@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).