public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66520] bad code generated code for branches with single & Date: Sun, 14 Jun 2015 12:26:00 -0000 [thread overview] Message-ID: <bug-66520-4-5llp97LE63@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66520-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66520 --- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Fisnik from comment #8) > To this end, the compiler should respect the code written by the developer. As far as the C++ standard is concerned the built-in && and & operators for type bool are equivalent if evaluating the operands has no side-effects. C++ is not a high-level assembly language. > I'm already having trouble with g++, as for the code with single &, it is > generating inefficient code. Or I have to remove completely the optimization > flag '-O3', but then I have a very slow code Have you tried just using -O3 -fno-xxx for the relevant pass?
prev parent reply other threads:[~2015-06-14 12:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-12 11:52 [Bug c++/66520] New: " fkastrati at gmail dot com 2015-06-13 10:13 ` [Bug c++/66520] " ebotcazou at gcc dot gnu.org 2015-06-13 23:21 ` fkastrati at gmail dot com 2015-06-14 7:23 ` ebotcazou at gcc dot gnu.org 2015-06-14 10:44 ` fkastrati at gmail dot com 2015-06-14 10:57 ` ebotcazou at gcc dot gnu.org 2015-06-14 10:58 ` schwab@linux-m68k.org 2015-06-14 11:26 ` fkastrati at gmail dot com 2015-06-14 11:34 ` fkastrati at gmail dot com 2015-06-14 12:26 ` redi at gcc dot gnu.org [this message]
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-66520-4-5llp97LE63@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).