public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zero at smallinteger dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95861] New: popcnt --- unnecessary leading xor instruction Date: Wed, 24 Jun 2020 08:42:41 +0000 [thread overview] Message-ID: <bug-95861-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95861 Bug ID: 95861 Summary: popcnt --- unnecessary leading xor instruction Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zero at smallinteger dot com Target Milestone: --- Created attachment 48778 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48778&action=edit sample code Consider the attached code, compiled with -O3 -mpopcnt. The assembly produced in gcc 9.3 is below (the same code is generated by gcc 10.x at godbolt). foo(unsigned long long): xor eax, eax popcnt rax, rdi ret The popcnt instruction will overwrite rax. Whether eax is cleared with xor has no effect. No xor instruction should be emitted in this case. For reference, trunk clang emits this code instead: foo(unsigned long long): # @foo(unsigned long long) popcnt rax, rdi ret This second code sample is as expected.
next reply other threads:[~2020-06-24 8:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-24 8:42 zero at smallinteger dot com [this message] 2020-06-24 8:55 ` [Bug target/95861] " jakub 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-95861-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).