public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110614] New: [14 Regression] ICE in vect_supportable_dr_alignment
Date: Mon, 10 Jul 2023 15:16:00 +0000	[thread overview]
Message-ID: <bug-110614-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110614
           Summary: [14 Regression] ICE in vect_supportable_dr_alignment
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dje at gcc dot gnu.org
  Target Milestone: ---
            Target: powerpc*-*-*

Beginning with

commit dd86a5a69cbda40cf76388a65d3317c91cb2b501
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Jun 22 11:40:46 2023 +0200

A number of GCC testsuite test cases ICE in vect_supportable_dr_alignment()

gcc/testsuite/gcc.dg/torture/pr68379.c

$ ./xgcc -B./ -S -O2 -mcpu=power7 pr68379.c 
during GIMPLE pass: vect
pr68379.c: In function ‘fn1’:
pr68379.c:6:1: internal compiler error: Segmentation fault
    6 | fn1 ()
      | ^~~
0x10c1d833 crash_signal
        /home/dje/src/gcc/gcc/toplev.cc:314
0x11b4ebd0 vect_supportable_dr_alignment(vec_info*, dr_vec_info*, tree_node*,
int)
        /home/dje/src/gcc/gcc/tree-vect-data-refs.cc:6833
0x11b53717 vect_enhance_data_refs_alignment(_loop_vec_info*)
        /home/dje/src/gcc/gcc/tree-vect-data-refs.cc:2044
0x10fc35bb vect_analyze_loop_2
        /home/dje/src/gcc/gcc/tree-vect-loop.cc:2783
0x10fc4d8f vect_analyze_loop_1
        /home/dje/src/gcc/gcc/tree-vect-loop.cc:3316
0x10fc56bb vect_analyze_loop(loop*, vec_info_shared*)
        /home/dje/src/gcc/gcc/tree-vect-loop.cc:3470
0x110174e7 try_vectorize_loop_1
        /home/dje/src/gcc/gcc/tree-vectorizer.cc:1064
0x110174e7 try_vectorize_loop
        /home/dje/src/gcc/gcc/tree-vectorizer.cc:1180
0x11017fa3 execute
        /home/dje/src/gcc/gcc/tree-vectorizer.cc:1296

The test cases succeed with Power8, Power9, or Power10, but ICE with
-mcpu=power7. command line option.

             reply	other threads:[~2023-07-10 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 15:16 dje at gcc dot gnu.org [this message]
2023-07-10 15:16 ` [Bug tree-optimization/110614] " dje at gcc dot gnu.org
2023-07-10 18:30 ` seurer at gcc dot gnu.org
2023-07-11  7:44 ` rguenth at gcc dot gnu.org
2023-07-11  8:54 ` rguenth at gcc dot gnu.org
2023-07-11 10:23 ` cvs-commit at gcc dot gnu.org
2023-07-11 10:31 ` 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-110614-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).