From: ami_stuff <ami_stuff@o2.pl>
To: gcc@gcc.gnu.org
Subject: Speed regression (m68k)
Date: Sat, 13 Jun 2009 20:20:00 -0000 [thread overview]
Message-ID: <d02a52f.7316a242.4a3409ff.ce0b@o2.pl> (raw)
Hi,
I notice about 20% speed regression with GCC 4.4.0 PNGCrush build compared to GCC 3.4.0 build (Amiga 68060@50MHz).
CFLAGS = -I. -DNO_FSEEKO -O2 -fomit-frame-pointer -Wall -m68060 -s
Here are the results:
GCC 3.4.0:
CPU time used = 267.340 seconds (decoding 16.940,
encoding 247.800, other 2.600 seconds)
GCC 4.4.0:
CPU time used = 328.360 seconds (decoding 16.800,
encoding 309.260, other 2.300 seconds)
Maybe someone with m68k Debian/PPC/x86 can compile PNGCrush with GCC 3.4.0 and GCC 4.4.0, so we will know if this regression happens there too?
Regards
next reply other threads:[~2009-06-13 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 20:20 ami_stuff [this message]
2009-06-15 19:19 ` Ian Lance Taylor
2009-06-15 23:46 ` ami_stuff
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=d02a52f.7316a242.4a3409ff.ce0b@o2.pl \
--to=ami_stuff@o2.pl \
--cc=gcc@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).