public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/55814] Missed optimization with short-circuit evaluation of always evaluated comparisons/loads Date: Wed, 26 Dec 2012 21:46:00 -0000 [thread overview] Message-ID: <bug-55814-4-LTVGphojMD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55814-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55814 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2012-12-26 Summary|Missed optimization with |Missed optimization with |short-circuit evaluation |short-circuit evaluation of | |always evaluated | |comparisons/loads Ever Confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-12-26 21:46:40 UTC --- This is a sinking issue. Sinking of loads. If the code was written as: _Bool foo(int *a, int *b) { return (a[0] > b[0]) || (a[1] > b[1]) || (a[2] > b[2]) || (a[3] > b[3]); } Instead then it would short-circuit correctly.
next prev parent reply other threads:[~2012-12-26 21:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-26 17:45 [Bug middle-end/55814] New: Missed optimization with short-circuit evaluation tkoenig at gcc dot gnu.org 2012-12-26 21:46 ` pinskia at gcc dot gnu.org [this message] 2012-12-27 17:24 ` [Bug middle-end/55814] Missed optimization with short-circuit evaluation of always evaluated comparisons/loads tkoenig at gcc dot gnu.org 2012-12-31 16:26 ` 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-55814-4-LTVGphojMD@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).