This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Speed regression (m68k)
- From: Ian Lance Taylor <iant at google dot com>
- To: ami_stuff <ami_stuff at o2 dot pl>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 15 Jun 2009 12:18:57 -0700
- Subject: Re: Speed regression (m68k)
- References: <d02a52f.7316a242.4a3409ff.ce0b@o2.pl>
ami_stuff <ami_stuff@o2.pl> writes:
> 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?
I assume that you are measuring the speed of the compiled code, not the
speed of the compiler itself. Can you open a bug report about this,
with enough information for other people to reproduce the results (e.g.,
pointer to source code being compiled and input file(s)). Thanks.
Ian