public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mfarazma.ext at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100884] New: Comparing unsigned 32 bit integer values generates 64 bit compare instructions when optimized Date: Wed, 02 Jun 2021 20:47:47 +0000 [thread overview] Message-ID: <bug-100884-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100884 Bug ID: 100884 Summary: Comparing unsigned 32 bit integer values generates 64 bit compare instructions when optimized Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mfarazma.ext at gmail dot com Target Milestone: --- **0.c** ``` #include <iostream> uint32_t codegen(); int main(){ uint32_t expected = (codegen()) != 0 ? -1 : -2; bool check_eq = expected == codegen(); if (!(check_eq)){ std::cout << "Check failed" << std::endl; } return 0; } ``` **1.cc** ``` #include <iostream> uint32_t codegen(){ volatile int64_t a = -1; return a; } ``` Compile it with optimization enabled: g++ -O3 0.cc 1.cc Checking the generate code shows this instruction is generated for ` if (!(check_eq)){...}`: ``` cmpd r31,r3 ``` Compiling the same code with gcc version 8.4.0 emits this instead which is correct: ``` cmpw cr7,r3,r31 ``` This issue is causing failures as the returned value from `codegen()` may not have its upper 32 bits cleared and using `cmpd` on it will create the wrong output.
next reply other threads:[~2021-06-02 20:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 20:47 mfarazma.ext at gmail dot com [this message] 2021-06-17 18:50 ` [Bug target/100884] " mfarazma.ext at gmail dot com 2021-06-17 18:51 ` mfarazma.ext at gmail dot com
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-100884-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).