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/114166] New: word_mode vectorization still relies on vector lowering Date: Thu, 29 Feb 2024 11:43:23 +0000 [thread overview] Message-ID: <bug-114166-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114166 Bug ID: 114166 Summary: word_mode vectorization still relies on vector lowering Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- When the vectorizer decides to use emulated vectors for operations the target doesn't support and the vector types do not have integer mode but the vectorizer simply emits vector code nevertheless which it does for bitwise operations, we fail RTL expansion. This can be seen with g++.dg/opt/pr82929.C when moving vector lowering before vectorization. We then vectorize V1SImode bitwise and even though the optab check discovered that's not supported. Vectorizer code generation should, like it now does for PLUS/MINUS and NEGATE, use integer types when code generating emulated vectors.
next reply other threads:[~2024-02-29 11:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-29 11:43 rguenth at gcc dot gnu.org [this message] 2024-02-29 11:44 ` [Bug tree-optimization/114166] " rguenth at gcc dot gnu.org 2024-02-29 11:48 ` rguenth at gcc dot gnu.org 2024-02-29 22:46 ` pinskia 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-114166-4@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).