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/109721] [14 Regression] predcom-2 started to fail on arc-elf after r14-391 Date: Thu, 04 May 2023 08:06:06 +0000 [thread overview] Message-ID: <bug-109721-4-WKM4u5HG0D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109721-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109721 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Huh, we indeed vectorize count_averages (). But I have no idea how the offending rev should have changed this ... Ah. Before we had gcc.dg/tree-ssa/predcom-2.c:27:55: missed: not vectorized: relevant stmt not supported: _9 = _8 & 65535; but now we let this slip through with gcc.dg/tree-ssa/predcom-2.c:26:17: note: proceeding using word mode. but we do not actually use word_mode. Later veclower decomposes the bitwise vector and: - vect__9.38_33 = vect__8.37_31 & { 65535, 65535 }; + _26 = BIT_FIELD_REF <vect__8.37_31, 32, 0>; + _19 = _26 & 65535; + _23 = BIT_FIELD_REF <vect__8.37_31, 32, 32>; + _10 = _23 & 65535; + vect__9.38_33 = {_19, _10}; Btw, when writing the patch I noticed we let SImode AND through when target_support_p even though it isn't word_mode and I didn't want to change that but had to catch the case where SImode PLUS is supported (well, obviously...) but emulated vectors rely on it being word_mode. I'm going to amend this more. But maybe this arch is also missing bit operation vector support for some unknown reason.
next prev parent reply other threads:[~2023-05-04 8:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 22:16 [Bug tree-optimization/109721] New: [14 Regression] predcom-2 fails after recent changes law at gcc dot gnu.org 2023-05-03 22:19 ` [Bug tree-optimization/109721] [14 Regression] predcom-2 started to fail on arc-elf after r14-391 pinskia at gcc dot gnu.org 2023-05-03 22:20 ` pinskia at gcc dot gnu.org 2023-05-04 6:16 ` rguenth at gcc dot gnu.org 2023-05-04 8:06 ` rguenth at gcc dot gnu.org [this message] 2023-05-04 10:52 ` cvs-commit at gcc dot gnu.org 2023-05-04 10:52 ` 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-109721-4-WKM4u5HG0D@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).