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/110436] New: ICE in vectorizable_live_operation, at tree-vect-loop.cc:10170
Date: Tue, 27 Jun 2023 11:22:56 +0000	[thread overview]
Message-ID: <bug-110436-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110436
           Summary: ICE in vectorizable_live_operation, at
                    tree-vect-loop.cc:10170
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jamborm at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-linux
            Target: aarch64-suse-linux

Using a cross compiler (revision r14-2079-g9326a49c9e9d63) configured with

  /home/worker/buildworker/tiber-gcc-trunk-aarch64/build/configure
--enable-languages=c,c++,fortran,rust,m2 --disable-bootstrap
--disable-libsanitizer --disable-multilib --enable-checking=release
--prefix=/home/worker/cross --target=aarch64-linux-gnu
--with-as=/usr/bin/aarch64-suse-linux-as

to compile our own testcase testsuite/gcc.dg/pr83089.c with -O3 results in an
ICE:

$ ~/cross/bin/aarch64-linux-gnu-gcc gcc/testsuite/gcc.dg/pr83089.c -O3 -o
/tmp/aaa.out
during GIMPLE pass: vect
gcc/testsuite/gcc.dg/pr83089.c: In function ‘it’:
gcc/testsuite/gcc.dg/pr83089.c:8:1: internal compiler error: in
vectorizable_live_operation, at tree-vect-loop.cc:10170
    8 | it (int zy, short int el)
      | ^~
0x744be1 vectorizable_live_operation(vec_info*, _stmt_vec_info*,
gimple_stmt_iterator*, _slp_tree*, _slp_instance*, int, bool,
vec<stmt_info_for_cost, va_heap, vl_ptr>*)
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-loop.cc:10170
0x187e8ac can_vectorize_live_stmts
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-stmts.cc:11694
0x18a5c53 vect_analyze_stmt(vec_info*, _stmt_vec_info*, bool*, _slp_tree*,
_slp_instance*, vec<stmt_info_for_cost, va_heap, vl_ptr>*)
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-stmts.cc:11928
0xf42c61 vect_analyze_loop_operations
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-loop.cc:2083
0xf42c61 vect_analyze_loop_2
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-loop.cc:2869
0xf44b00 vect_analyze_loop_1
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-loop.cc:3301
0xf45261 vect_analyze_loop(loop*, vec_info_shared*)
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vect-loop.cc:3455
0xf7eed5 try_vectorize_loop_1
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vectorizer.cc:1064
0xf7eed5 try_vectorize_loop
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vectorizer.cc:1180
0xf7f70c execute
       
/home/worker/buildworker/tiber-gcc-trunk-aarch64/build/gcc/tree-vectorizer.cc:1296
Please submit a full bug report, with preprocessed source (by using
-freport-bug).

             reply	other threads:[~2023-06-27 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 11:22 jamborm at gcc dot gnu.org [this message]
2023-06-27 13:22 ` [Bug tree-optimization/110436] " acoplan at gcc dot gnu.org
2023-06-27 14:01 ` [Bug tree-optimization/110436] [14 Regression] " acoplan at gcc dot gnu.org
2023-06-27 15:21 ` avieira at gcc dot gnu.org
2023-06-27 15:22 ` avieira at gcc dot gnu.org
2023-06-27 19:46 ` pinskia at gcc dot gnu.org
2023-07-04  8:40 ` cvs-commit at gcc dot gnu.org
2023-07-04  9:01 ` 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-110436-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).