public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101242] New: Segfault in SLP vectorizor after 2ad71efb5de
Date: Mon, 28 Jun 2021 13:30:28 +0000	[thread overview]
Message-ID: <bug-101242-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101242
           Summary: Segfault in SLP vectorizor after 2ad71efb5de
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jamborm at gcc dot gnu.org
                CC: rguenth at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-linux
            Target: x86_64-linux

Since commit 2ad71efb5de (fix BB reduc permute elide with life stmts), the
following testcase (reduced from 433.milc) ICEs for me when compiled at -Ofast
(on x86_64-linux with generic march):

typedef struct {
  double real;
  double imag;
} complex;
typedef struct {
  complex e[3][3];
} su3_matrix;
su3_matrix check_su3_c;
double check_su3_ar, check_su3_ari, check_su3_max;
int arireturn();
int check_su3() {
  check_su3_ar = check_su3_c.e[0][0].real * check_su3_c.e[1][0].real +
                 check_su3_c.e[0][0].imag * check_su3_c.e[1][0].imag +
                 check_su3_c.e[0][1].real * check_su3_c.e[1][1].real +
                 check_su3_c.e[0][1].imag * check_su3_c.e[1][1].imag +
                 check_su3_c.e[0][2].real * check_su3_c.e[1][2].real +
                 check_su3_c.e[0][2].imag * check_su3_c.e[1][2].imag;
  check_su3_max = check_su3_c.e[0][0].real * check_su3_c.e[2][0].real +
                  check_su3_c.e[0][0].imag * check_su3_c.e[2][0].imag +
                  check_su3_c.e[0][1].real * check_su3_c.e[2][1].real +
                  check_su3_c.e[0][1].imag * check_su3_c.e[2][1].imag +
                  check_su3_c.e[0][2].real * check_su3_c.e[2][2].real +
                  check_su3_c.e[0][2].imag * check_su3_c.e[2][2].imag;
  check_su3_ari = check_su3_ar;
  if (check_su3_ari)
    check_su3_max = check_su3_c.e[1][0].real * check_su3_c.e[2][0].real +
                    check_su3_c.e[1][0].imag * check_su3_c.e[2][0].imag +
                    check_su3_c.e[1][1].real * check_su3_c.e[2][1].real +
                    check_su3_c.e[1][1].imag * check_su3_c.e[2][1].imag +
                    check_su3_c.e[1][2].real * check_su3_c.e[2][2].real +
                    check_su3_c.e[1][2].imag * check_su3_c.e[2][2].imag;
  if (check_su3_max)
    arireturn();
  return 0;
}

             reply	other threads:[~2021-06-28 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 13:30 jamborm at gcc dot gnu.org [this message]
2021-06-28 13:32 ` [Bug tree-optimization/101242] " jamborm at gcc dot gnu.org
2021-06-28 13:34 ` [Bug tree-optimization/101242] Segfault in SLP vectorizor after g:2ad71efb5de marxin at gcc dot gnu.org
2021-06-28 17:32 ` jamborm at gcc dot gnu.org
2021-06-28 21:40 ` dcb314 at hotmail dot com
2021-06-29  7:06 ` rguenth at gcc dot gnu.org
2021-06-29  7:51 ` dcb314 at hotmail dot com
2021-06-29  8:35 ` cvs-commit at gcc dot gnu.org
2021-06-29  8:35 ` rguenth at gcc dot gnu.org
2021-06-29  8:36 ` rguenth 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-101242-4@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).