public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wbrana at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54077] [4.7/4.8 Regression] Bytemark FP EMULATION 44% slower than with clang
Date: Wed, 01 Aug 2012 22:35:00 -0000	[thread overview]
Message-ID: <bug-54077-4-hP3WPQMSmY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54077-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54077

--- Comment #10 from wbrana <wbrana at gmail dot com> 2012-08-01 22:35:29 UTC ---
Reversion of 175752 on latest 4.7 branch improved FP EMU by 41%, but made
ASSIGNMENT worse by 8%.

with 175752

NUMERIC SORT        :          1562.9  :      40.08  :      13.16
STRING SORT         :          730.08  :     326.22  :      50.49
BITFIELD            :       5.956e+08  :     102.17  :      21.34
FP EMULATION        :          232.96  :     111.79  :      25.79
FOURIER             :           36191  :      41.16  :      23.12
ASSIGNMENT          :          63.469  :     241.51  :      62.64
IDEA                :            9512  :     145.48  :      43.20
HUFFMAN             :          3475.8  :      96.38  :      30.78
NEURAL NET          :          80.296  :     128.99  :      54.26
LU DECOMPOSITION    :          2696.9  :     139.71  :     100.89

without 175752

NUMERIC SORT        :          1526.9  :      39.16  :      12.86
STRING SORT         :          724.96  :     323.93  :      50.14
BITFIELD            :       5.962e+08  :     102.27  :      21.36
FP EMULATION        :          328.32  :     157.54  :      36.35
FOURIER             :           36275  :      41.26  :      23.17
ASSIGNMENT          :           58.37  :     222.11  :      57.61
IDEA                :            9480  :     144.99  :      43.05
HUFFMAN             :          3453.1  :      95.75  :      30.58
NEURAL NET          :          79.128  :     127.11  :      53.47
LU DECOMPOSITION    :          2733.4  :     141.60  :     102.25


  parent reply	other threads:[~2012-08-01 22:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  9:38 [Bug tree-optimization/54077] New: " wbrana at gmail dot com
2012-07-24  9:39 ` [Bug tree-optimization/54077] " wbrana at gmail dot com
2012-07-24  9:41 ` wbrana at gmail dot com
2012-07-24  9:42 ` wbrana at gmail dot com
2012-07-24  9:43 ` wbrana at gmail dot com
2012-07-31  9:36 ` rguenth at gcc dot gnu.org
2012-07-31 10:12 ` wbrana at gmail dot com
2012-07-31 22:45 ` [Bug tree-optimization/54077] [4.7/4.8 Regression] " wbrana at gmail dot com
2012-08-01 11:00 ` wbrana at gmail dot com
2012-08-01 18:46 ` ubizjak at gmail dot com
2012-08-01 22:35 ` wbrana at gmail dot com [this message]
2012-08-05 10:57 ` wbrana at gmail dot com
2012-08-27  8:43 ` wbrana at gmail dot com
2012-09-07 10:15 ` rguenth at gcc dot gnu.org
2012-09-20 10:20 ` jakub at gcc dot gnu.org
2012-10-04 14:25 ` wbrana at gmail dot com
2012-11-11 16:37 ` [Bug tree-optimization/54077] Bytemark FP EMULATION 9%-15% " wbrana at gmail dot com
2012-11-12 13:17 ` wbrana at gmail dot com
2013-04-11  7:59 ` rguenth at gcc dot gnu.org
2014-06-12 13:53 ` 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-54077-4-hP3WPQMSmY@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: link
Be 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).