public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38922] [4.3 Regression] Optimization regression in simple conditional code (js instead of cmov) 4.3 vs 4.1 and 3.4 Date: Tue, 20 Jan 2009 09:04:00 -0000 [thread overview] Message-ID: <20090120090434.1188.qmail@sourceware.org> (raw) In-Reply-To: <bug-38922-16413@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2009-01-20 09:04 ------- 4.4.0 is faster for me than 4.2 and 4.3 (4.3 is indeed slower than 4.2, but my 3.4 (32bit only) is way slower than 4.4 (also 32bit)). Note that performance of cmov heavily depends on the microarchitecture of your CPU (I measured on a AMD K8). -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Known to fail| |4.3.2 Known to work| |3.4.6 4.4.0 Summary|Optimization regression in |[4.3 Regression] |simple conditional code (js |Optimization regression in |instead of cmov) 4.3 vs 4.1 |simple conditional code (js |and 3.4 |instead of cmov) 4.3 vs 4.1 | |and 3.4 Target Milestone|--- |4.3.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38922
next prev parent reply other threads:[~2009-01-20 9:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-20 8:45 [Bug c/38922] New: " vincenzo dot innocente at cern dot ch 2009-01-20 8:48 ` [Bug c/38922] " vincenzo dot innocente at cern dot ch 2009-01-20 9:04 ` rguenth at gcc dot gnu dot org [this message] 2009-01-20 9:24 ` [Bug c/38922] [4.3 Regression] " vincenzo dot innocente at cern dot ch 2009-01-24 10:28 ` [Bug target/38922] " rguenth at gcc dot gnu dot org 2009-02-21 13:13 ` rguenth at gcc dot gnu dot org 2009-04-22 15:21 ` rguenth at gcc dot gnu dot 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=20090120090434.1188.qmail@sourceware.org \ --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).