public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106237] New: [13 regression] serveral tests begin ICEing starting with r13-1575-gcf3a120084e946
Date: Fri, 08 Jul 2022 19:37:36 +0000	[thread overview]
Message-ID: <bug-106237-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106237
           Summary: [13 regression] serveral tests begin ICEing starting
                    with r13-1575-gcf3a120084e946
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:cf3a120084e94614a4917f71940325cd4b537f24, r13-1575-gcf3a120084e946

Related to, or maybe the same as, the later failure reported for power 7 BE in
PR106228 perhaps?  These fail in the same place but fail for power 8, 9, and 10
little endian and power 8 big endian.

FAIL: gcc.target/powerpc/pr56605.c (internal compiler error: in
vect_transform_loops, at tree-vectorizer.cc:1032)
FAIL: gcc.target/powerpc/pr56605.c (test for excess errors)
FAIL: gcc.target/powerpc/pr60137.c (internal compiler error: in
vect_transform_loops, at tree-vectorizer.cc:1032)
FAIL: gcc.target/powerpc/pr60137.c (test for excess errors)
FAIL: gcc.target/powerpc/vsx-vectorize-2.c (internal compiler error: in
vect_transform_loops, at tree-vectorizer.cc:1032)
FAIL: gcc.target/powerpc/vsx-vectorize-2.c (test for excess errors)
FAIL: gcc.target/powerpc/vsx-vectorize-2.c scan-tree-dump-times vect
"vectorized 1 loops" 1
FAIL: gcc.target/powerpc/vsx-vectorize-3.c (internal compiler error: in
vect_transform_loops, at tree-vectorizer.cc:1032)
FAIL: gcc.target/powerpc/vsx-vectorize-3.c (test for excess errors)
FAIL: gcc.target/powerpc/vsx-vectorize-3.c scan-tree-dump-times vect
"vectorized 1 loops" 1
FAIL: gcc.target/powerpc/vsx-vectorize-7.c (internal compiler error: in
vect_transform_loops, at tree-vectorizer.cc:1032)
FAIL: gcc.target/powerpc/vsx-vectorize-7.c (test for excess errors)
FAIL: gcc.target/powerpc/vsx-vectorize-7.c scan-tree-dump-times vect
"vectorized 1 loops" 1

spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr56605.c
-fdiagnostics-plain-output -O3 -mvsx -mdejagnu-cpu=power7 -fno-unroll-loops
-fdump-rtl-combine -ffat-lto-objects -S -o pr56605.s
during GIMPLE pass: vect
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr56605.c: In
function 'foo':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.target/powerpc/pr56605.c:7:6:
internal compiler error: in vect_transform_loops, at tree-vectorizer.cc:1032
0x1104fca3 vect_transform_loops
        /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.cc:1032
0x1105016f try_vectorize_loop_1
        /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.cc:1153
0x1105016f try_vectorize_loop
        /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.cc:1183
0x110508f3 execute
        /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.cc:1299


commit cf3a120084e94614a4917f71940325cd4b537f24 (HEAD, refs/bisect/bad)
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Jul 8 10:41:59 2022 +0200

    tree-optimization/106226 - move vectorizer virtual SSA update

             reply	other threads:[~2022-07-08 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 19:37 seurer at gcc dot gnu.org [this message]
2022-07-11  6:46 ` [Bug tree-optimization/106237] " rguenth at gcc dot gnu.org
2022-07-11 15:40 ` seurer at gcc dot gnu.org
2022-07-13  6:04 ` rguenth at gcc dot gnu.org
2022-07-15 20:16 ` seurer 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-106237-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).