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/104501] New: vector lowering for VEC_COND_EXPR does not consider smaller vectors Date: Fri, 11 Feb 2022 12:58:38 +0000 [thread overview] Message-ID: <bug-104501-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104501 Bug ID: 104501 Summary: vector lowering for VEC_COND_EXPR does not consider smaller vectors Product: gcc Version: 12.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: --- The following C++ testcase is decomposed to scalar operations by vector lowering when compiling with just SSE2 support. But when using a vector size of 16 we can produce optimized code. typedef int vsi __attribute__((vector_size(32))); vsi res, v1, v2, v3, v4; void foo () { res = v1 == v2 ? v3 : v4; }
next reply other threads:[~2022-02-11 12:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-11 12:58 rguenth at gcc dot gnu.org [this message] 2022-02-11 18:17 ` [Bug tree-optimization/104501] " pinskia at gcc dot gnu.org 2022-02-14 7:14 ` 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-104501-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).