public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103941] New: uavgv2qi3_ceil is not used Date: Fri, 07 Jan 2022 15:31:03 +0000 [thread overview] Message-ID: <bug-103941-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103941 Bug ID: 103941 Summary: uavgv2qi3_ceil is not used Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ubizjak at gmail dot com Target Milestone: --- Following testcase: unsigned char ur[16], ua[16], ub[16]; void avgu_v2qi (void) { int i; for (i = 0; i < 2; i++) ur[i] = (ua[i] + ub[i] + 1) >> 1; } does not vectorize on x86_64-linux-gnu with -O2 -ftree-vectorize.
next reply other threads:[~2022-01-07 15:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-07 15:31 ubizjak at gmail dot com [this message] 2022-01-10 10:53 ` [Bug tree-optimization/103941] uavgv2qi3_ceil is not used (SLP costing and patterns vs live stmts) rguenth at gcc dot gnu.org 2022-01-10 12:49 ` rguenth at gcc dot gnu.org 2022-01-12 19:57 ` cvs-commit at gcc dot gnu.org 2022-01-26 12:42 ` rguenth at gcc dot gnu.org 2022-04-19 14:42 ` cvs-commit at gcc dot gnu.org 2022-04-19 14:44 ` 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-103941-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).