public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Speed regression (m68k)
@ 2009-06-13 20:20 ami_stuff
  2009-06-15 19:19 ` Ian Lance Taylor
  0 siblings, 1 reply; 3+ messages in thread
From: ami_stuff @ 2009-06-13 20:20 UTC (permalink / raw)
  To: gcc

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


^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Speed regression (m68k)
  2009-06-13 20:20 Speed regression (m68k) ami_stuff
@ 2009-06-15 19:19 ` Ian Lance Taylor
  2009-06-15 23:46   ` ami_stuff
  0 siblings, 1 reply; 3+ messages in thread
From: Ian Lance Taylor @ 2009-06-15 19:19 UTC (permalink / raw)
  To: ami_stuff; +Cc: gcc

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

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Speed regression (m68k)
  2009-06-15 19:19 ` Ian Lance Taylor
@ 2009-06-15 23:46   ` ami_stuff
  0 siblings, 0 replies; 3+ messages in thread
From: ami_stuff @ 2009-06-15 23:46 UTC (permalink / raw)
  To: Ian Lance Taylor; +Cc: gcc

Hi,

> I assume that you are measuring the speed of the compiled code, not the
> speed of the compiler itself.

Yes.

> 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)).

Done. Bug #40454.

Regards

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-06-15 23:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-06-13 20:20 Speed regression (m68k) ami_stuff
2009-06-15 19:19 ` Ian Lance Taylor
2009-06-15 23:46   ` ami_stuff

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).