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/109473] [10 Regression] ICE during GIMPLE pass: vect: verify_gimple failed with -O1 -ftree-loop-vectorize since r10-4076-g82e8e335f917b9
Date: Wed, 03 May 2023 08:45:53 +0000	[thread overview]
Message-ID: <bug-109473-4-Eac8SePmZD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109473-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The testcase fails for me in gcc 11 on both x86_64-linux and i686-linux
(--enable-checking=yes,rtl,extra):
+FAIL: gcc.dg/vect/pr109473.c (internal compiler error)
+FAIL: gcc.dg/vect/pr109473.c (test for excess errors)
+FAIL: gcc.dg/vect/pr109473.c -flto -ffat-lto-objects (internal compiler error)
+FAIL: gcc.dg/vect/pr109473.c -flto -ffat-lto-objects (test for excess errors)
/usr/src/gcc-11/gcc/testsuite/gcc.dg/vect/pr109473.c:7:6: internal compiler
error: in build_vector_from_val, at tree.c:1970
0x7cd0c6 build_vector_from_val(tree_node*, tree_node*)
        ../../gcc/tree.c:1970
0xd77c26 gimple_build_vector_from_val(gimple**, unsigned int, tree_node*,
tree_node*)
        ../../gcc/gimple-fold.c:8719
0x12fc798 gimple_build_vector_from_val(gimple**, tree_node*, tree_node*)
        ../../gcc/gimple-fold.h:142
0x12fc798 get_initial_def_for_reduction
        ../../gcc/tree-vect-loop.c:4765
0x12fc798 vect_transform_cycle_phi(_loop_vec_info*, _stmt_vec_info*, gimple**,
_slp_tree*, _slp_instance*)
        ../../gcc/tree-vect-loop.c:7681
0x12ece28 vect_transform_stmt(vec_info*, _stmt_vec_info*,
gimple_stmt_iterator*, _slp_tree*, _slp_instance*)
        ../../gcc/tree-vect-stmts.c:11012
0x13053f5 vect_transform_loop(_loop_vec_info*, gimple*)
        ../../gcc/tree-vect-loop.c:9633
0x1336a3c try_vectorize_loop_1
        ../../gcc/tree-vectorizer.c:1104
0x13376a1 vectorize_loops()
        ../../gcc/tree-vectorizer.c:1243

  parent reply	other threads:[~2023-05-03  8:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 14:48 [Bug tree-optimization/109473] New: ICE during GIMPLE pass: vect: verify_gimple failed with -m32 arsen at gcc dot gnu.org
2023-04-11 14:55 ` [Bug tree-optimization/109473] ICE during GIMPLE pass: vect: verify_gimple failed with -O1 -ftree-loop-vectorize arsen at gcc dot gnu.org
2023-04-11 15:13 ` [Bug tree-optimization/109473] [10/11/12/13 Regression] " jakub at gcc dot gnu.org
2023-04-12  8:00 ` [Bug tree-optimization/109473] [10/11/12/13 Regression] ICE during GIMPLE pass: vect: verify_gimple failed with -O1 -ftree-loop-vectorize since r10-4076-g82e8e335f917b9 rguenth at gcc dot gnu.org
2023-04-12  8:06 ` jakub at gcc dot gnu.org
2023-04-12 10:23 ` cvs-commit at gcc dot gnu.org
2023-04-12 10:24 ` [Bug tree-optimization/109473] [10/11/12 " rguenth at gcc dot gnu.org
2023-04-12 10:53 ` arsen at gcc dot gnu.org
2023-04-17  9:14 ` cvs-commit at gcc dot gnu.org
2023-05-02 12:03 ` [Bug tree-optimization/109473] [10/11 " cvs-commit at gcc dot gnu.org
2023-05-03  8:45 ` jakub at gcc dot gnu.org [this message]
2023-05-03 10:14 ` [Bug tree-optimization/109473] [10 " cvs-commit at gcc dot gnu.org
2023-07-07 10:07 ` 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-109473-4-Eac8SePmZD@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).