public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104595] unvectorized loop due to bool condition loaded from memory Date: Mon, 21 Feb 2022 13:26:38 +0000 [thread overview] Message-ID: <bug-104595-4-xa4KSRVFvw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104595-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104595 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- The patch doesn't really work, it regresses some AVX512 stuff in i386.exp, notably FAIL: gcc.target/i386/avx512vl-vdivps-2.c (internal compiler error: in vect_get_ vec_defs_for_operand, at tree-vect-stmts.cc:1508) ... FAIL: gcc.target/i386/mask-pack-prefer128.c scan-tree-dump-times vect "vectorized 1 loops" 10 FAIL: gcc.target/i386/mask-pack-prefer256.c scan-tree-dump-times vect "vectorized 1 loops" 10 FAIL: gcc.target/i386/mask-pack.c scan-tree-dump-times vect "vectorized 1 loops" 10 FAIL: gcc.target/i386/mask-unpack.c scan-tree-dump-times vect "vectorized 1 loops" 10 There's an additional case: #define N 256 typedef short T; extern T a[N]; extern T b[N]; extern T c[N]; extern _Bool pb[N]; void predicate_by_bool() { for (int i = 0; i < N; i++) c[i] = pb[i] ? a[i] : b[i]; } where we expect vect_recog_mask_conversion_pattern to trigger here. That case can be fixed with @@ -4658,9 +4660,9 @@ vect_recog_mask_conversion_pattern (vec_info *vinfo, if (TREE_CODE (rhs1) == SSA_NAME) { - rhs1_type = integer_type_for_mask (rhs1, vinfo); - if (!rhs1_type) + if (integer_type_for_mask (rhs1, vinfo)) return NULL; + rhs1_type = TREE_TYPE (rhs1); } else if (COMPARISON_CLASS_P (rhs1)) { but we then run into the original issue again: t.c:10:6: missed: not vectorized: relevant stmt not supported: patt_28 = (<signed-boolean:16>) _1; The cruical difference between working and not working is the _1 != 0 ?: vs. _1 ?: - I think we do have a duplicate bugreport here, possibly involving combinations of different from memory bools. Trying to make bool pattern recog inserting the relevant compensation code is really iffy, the mask conversion pattern confuses things here - what we are missing seems really be transforming the leafs. Note that we do not try to patter-recog a pattern thus we cannot at the moment have both, vect_recog_bool_pattern and vect_recog_mask_conversion_pattern at the same time on the ?: stmt. Note IIRC vect_recog_bool_pattern has to come last but it's now after vect_recog_mask_conversion_pattern. Unfortunately swapping things does not make vect_recog_bool_pattern recognize and fixup patt_24 = (<signed-boolean:16>) _1;
next prev parent reply other threads:[~2022-02-21 13:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 10:05 [Bug tree-optimization/104595] New: " linkw at gcc dot gnu.org 2022-02-18 10:27 ` [Bug tree-optimization/104595] " rguenth at gcc dot gnu.org 2022-02-18 16:26 ` segher at gcc dot gnu.org 2022-02-20 3:52 ` pinskia at gcc dot gnu.org 2022-02-20 3:58 ` pinskia at gcc dot gnu.org 2022-02-21 7:54 ` rguenth at gcc dot gnu.org 2022-02-21 10:01 ` rguenth at gcc dot gnu.org 2022-02-21 13:26 ` rguenth at gcc dot gnu.org [this message] 2022-02-21 13:45 ` rguenth at gcc dot gnu.org 2022-02-23 7:18 ` linkw at gcc dot gnu.org 2022-02-23 7:41 ` rguenther at suse dot de 2022-02-23 8:55 ` linkw at gcc dot gnu.org 2022-05-05 8:37 ` cvs-commit at gcc dot gnu.org 2022-05-05 8:39 ` 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-104595-4-xa4KSRVFvw@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).