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/109176] [13 Regression] internal compiler error: in to_constant, at poly-int.h:504 Date: Tue, 21 Mar 2023 10:28:39 +0000 [thread overview] Message-ID: <bug-109176-4-jEckzMpxPF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109176-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109176 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Richard Biener from comment #7) > --- a/gcc/tree-vect-generic.cc > +++ b/gcc/tree-vect-generic.cc > @@ -1040,6 +1040,10 @@ expand_vector_condition (gimple_stmt_iterator *gsi, > bitmap dce_ssa_names) > tree_code code = TREE_CODE (a); > gassign *assign = NULL; > > + if (VECTOR_BOOLEAN_TYPE_P (TREE_TYPE (a)) > + && expand_vec_cond_expr_p (type, TREE_TYPE (a), ERROR_MARK)) > + return true; > + > if (code == SSA_NAME) > { > assign = dyn_cast<gassign *> (SSA_NAME_DEF_STMT (a)); Ok, the above LGTM. > @@ -1053,14 +1057,14 @@ expand_vector_condition (gimple_stmt_iterator *gsi, > bitmap dce_ssa_names) > comp_inner_type = TREE_TYPE (TREE_TYPE (a1)); > comp_width = vector_element_bits_tree (TREE_TYPE (a1)); > } > - } > > - if (expand_vec_cond_expr_p (type, TREE_TYPE (a1), code) > - || (integer_all_onesp (b) && integer_zerop (c) > - && expand_vec_cmp_expr_p (type, TREE_TYPE (a1), code))) > - { > - gcc_assert (TREE_CODE (a) == SSA_NAME || TREE_CODE (a) == VECTOR_CST); > - return true; > + if (expand_vec_cond_expr_p (type, TREE_TYPE (a1), code) > + || (integer_all_onesp (b) && integer_zerop (c) > + && expand_vec_cmp_expr_p (type, TREE_TYPE (a1), code))) > + { > + gcc_assert (TREE_CODE (a) == SSA_NAME || TREE_CODE (a) == > VECTOR_CST); > + return true; > + } > } > > /* Handle vector boolean types with bitmasks. If there is a comparison Is the second hunk because the verifier now requires that first argument of VEC_COND_EXPR is always is_gimple_val and so it will be never tcc_comparison? I don't understand the assert after the change though, this is in code guarded with code == SSA_NAME, so TREE_CODE (a) == SSA_NAME is always true. If TREE_CODE (a) == VECTOR_CST, then it could return true without lowering only in the first hunk. Are you going to test the patch (with the assert removed?)? Not really sure about the testcase, perhaps the #c6 one in gcc.target/aarch64/sve/pr109176.c with /* PR tree-optimization/109176 */ /* { dg-do compile } */ /* { dg-options "-O2 -march=armv8.2-a+sve" } */ at the start added? Or #pragma GCC aarch64 "arm_sve.h" line replaced with #include <arm_sve.h> as well?
next prev parent reply other threads:[~2023-03-21 10:28 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-17 16:19 [Bug c++/109176] New: " malat at debian dot org 2023-03-17 16:43 ` [Bug c++/109176] " malat at debian dot org 2023-03-17 17:54 ` [Bug tree-optimization/109176] " ktkachov at gcc dot gnu.org 2023-03-20 9:17 ` [Bug tree-optimization/109176] [13 Regression] " rguenth at gcc dot gnu.org 2023-03-20 9:37 ` ktkachov at gcc dot gnu.org 2023-03-20 13:59 ` jakub at gcc dot gnu.org 2023-03-20 15:35 ` jakub at gcc dot gnu.org 2023-03-21 9:25 ` jakub at gcc dot gnu.org 2023-03-21 9:53 ` rguenth at gcc dot gnu.org 2023-03-21 10:28 ` jakub at gcc dot gnu.org [this message] 2023-03-21 10:41 ` jakub at gcc dot gnu.org 2023-03-21 10:57 ` ktkachov at gcc dot gnu.org 2023-03-21 12:03 ` jakub at gcc dot gnu.org 2023-03-21 12:12 ` rguenth at gcc dot gnu.org 2023-03-22 8:47 ` jakub at gcc dot gnu.org 2023-03-22 12:03 ` jakub at gcc dot gnu.org 2023-03-22 12:08 ` jakub at gcc dot gnu.org 2023-03-23 9:04 ` cvs-commit at gcc dot gnu.org 2023-03-23 9:08 ` [Bug tree-optimization/109176] [11/12 " jakub at gcc dot gnu.org 2023-04-18 7:15 ` cvs-commit at gcc dot gnu.org 2023-04-18 7:21 ` [Bug tree-optimization/109176] [11 " jakub at gcc dot gnu.org 2023-04-26 6:58 ` rguenth at gcc dot gnu.org 2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org 2023-05-03 10:45 ` jakub 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-109176-4-jEckzMpxPF@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: linkBe 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).