public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "llvm at rifkin dot dev" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101822] New: Codegen bug for popcount Date: Sun, 08 Aug 2021 22:59:19 +0000 [thread overview] Message-ID: <bug-101822-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101822 Bug ID: 101822 Summary: Codegen bug for popcount Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: llvm at rifkin dot dev Target Milestone: --- GCC cleverly optimizes the following loop into a popcount intrinsic: uint32_t foo(uint32_t n) { uint32_t count = 0; while(n) { n &= n - 1; count++; } return count; } But the generated assembly is highly redundant https://godbolt.org/z/nbGb13G5W: foo(unsigned int): xor eax, eax xor edx, edx popcnt eax, edi test edi, edi cmove eax, edx ret if(n == 0) __builtin_unreachable(); does seem to help the compiler's analysis. It seems here the compiler is not realizing both the loop and popcnt intrinsic are well-defined for n == 0. This is closely related to another bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101821.
next reply other threads:[~2021-08-08 22:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-08 22:59 llvm at rifkin dot dev [this message] 2021-08-08 23:10 ` [Bug tree-optimization/101822] " llvm at rifkin dot dev 2021-08-08 23:17 ` pinskia at gcc dot gnu.org 2021-08-09 11:55 ` llvm at rifkin dot dev 2022-02-02 5:02 ` pinskia at gcc dot gnu.org 2023-10-24 11:20 ` 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-101822-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).