public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108608] [12/13 Regression] AArch64 vectorizer ICE in vect_transform_reduction
Date: Mon, 30 Jan 2023 21:50:27 +0000	[thread overview]
Message-ID: <bug-108608-4-vmigmse7TN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108608-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |12.3
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
                 CC|                            |rsandifo at gcc dot gnu.org
   Last reconfirmed|                            |2023-01-30
           Priority|P3                          |P2

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
during GIMPLE pass: vect
rh2164522.ii: In function ‘foo’:
rh2164522.ii:2:1: internal compiler error: in vect_transform_reduction, at
tree-vect-loop.cc:7758
    2 | foo ()
      | ^~~
0x19243a1 vect_transform_reduction(_loop_vec_info*, _stmt_vec_info*,
gimple_stmt_iterator*, gimple**, _slp_tree*)
        ../../gcc/tree-vect-loop.cc:7758
0x2a0f09b vect_transform_stmt(vec_info*, _stmt_vec_info*,
gimple_stmt_iterator*, _slp_tree*, _slp_instance*)
        ../../gcc/tree-vect-stmts.cc:11418
0x192e5cf vect_transform_loop_stmt
        ../../gcc/tree-vect-loop.cc:10562
0x192fd54 vect_transform_loop(_loop_vec_info*, gimple*)
        ../../gcc/tree-vect-loop.cc:11000
0x1988ece vect_transform_loops
        ../../gcc/tree-vectorizer.cc:1007
0x1989639 try_vectorize_loop_1
        ../../gcc/tree-vectorizer.cc:1153
0x1989772 try_vectorize_loop
        ../../gcc/tree-vectorizer.cc:1183
0x1989a05 execute
        ../../gcc/tree-vectorizer.cc:1299
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

  reply	other threads:[~2023-01-30 21:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 21:49 [Bug tree-optimization/108608] New: " jakub at gcc dot gnu.org
2023-01-30 21:50 ` jakub at gcc dot gnu.org [this message]
2023-01-30 21:55 ` [Bug tree-optimization/108608] [12/13 Regression] AArch64 vectorizer ICE in vect_transform_reduction and __builtin_fmax jakub at gcc dot gnu.org
2023-01-30 21:59 ` pinskia at gcc dot gnu.org
2023-01-30 22:03 ` pinskia at gcc dot gnu.org
2023-01-30 22:09 ` jakub at gcc dot gnu.org
2023-01-30 22:14 ` jakub at gcc dot gnu.org
2023-01-30 22:51 ` rsandifo at gcc dot gnu.org
2023-01-31 15:03 ` cvs-commit at gcc dot gnu.org
2023-04-03  8:58 ` [Bug tree-optimization/108608] [12 " cvs-commit at gcc dot gnu.org
2023-04-03  9:03 ` rsandifo 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-108608-4-vmigmse7TN@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).