public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rask Ingemann Lambertsen" <rask@kampsax.k-net.dk>
To: "EGCS mailing list" <egcs@cygnus.com>
Subject: Re: Performance measurements
Date: Mon, 29 Jun 1998 22:34:00 -0000	[thread overview]
Message-ID: <1748.484T1246T11154518@kampsax.k-net.dk> (raw)
In-Reply-To: <199806240851.KAA06049@keksy.mchp.siemens.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]

Den 24-Jun-98 10:51:03 skrev Martin Kahlert følgende om "Performance measurements":
> Hi,
> i tried to compare different compilers on my numerical code.
> Therefore i extracted a FPU intensive function and surrounded
> it with a loop while measuring the execution time.

It is also very memcpy() intensive. If your C library's memcpy() isn't very
good, you can gain quite some performance. I went from 34 MFLOPS to 59 MFLOPS
just by optimizing memcpy().

Here are some PowerPC 604e, 200 MHz results:

AmigaOS:
gcc version egcs-2.90.23 980102 (egcs-1.0.1 release)
-DPI=M_PI -O3 -fomit-frame-pointer -mcpu=604 -mmultiple -mstring
59.28 MFLOPS

AmigaOS:
gcc version 2.7.2.1
-DPI=M_PI -O3 -fomit-frame-pointer -mcpu=604 -mmultiple -mstring
54.15 MFLOPS

AIX (RS6000 43P):
gcc version 2.6.3
-DPI=M_PI -O3 -fomit-frame-pointer -mcpu=604 -Wa,-m604
54.68 MFLOPS

AIX (RS6000 43P):
Vendor supplied cc
-DPI=M_PI -O3 -qstrict
63.28 MFLOPS

AIX (RS6000 43P):
Vendor supplied cc
-DPI=M_PI -O3 -qstrict -qarch=ppc -qtune=604
60.89 MFLOPS

(?)

At least the performance is heading in the right direction, but it looks on
the low side low to me. Perhaps someone with a more recent PowerPC EGCS
build could be persuaded to post some results?

Regards,

/¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯T¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯\
| Rask Ingemann Lambertsen       | E-mail: mailto:rask@kampsax.k-net.dk  |
| Registered Phase5 developer    | WWW: http://www.gbar.dtu.dk/~c948374/ |
| A4000, 775 kkeys/s (RC5-64)    | "ThrustMe" on XPilot, ARCnet and IRC  |
|                           LOAD "emacs",8,1                             |


  parent reply	other threads:[~1998-06-29 22:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-24  2:28 Martin Kahlert
1998-06-24  8:51 ` David S. Miller
1998-06-24 10:08 ` Gerald Pfeifer
     [not found] ` <3590D5AE.167EB0E7@iis.fhg.de>
     [not found]   ` <19980624124843.A15248@keksy.mchp.siemens.de>
     [not found]     ` <3591031A.2781E494@iis.fhg.de>
     [not found]       ` <19980624170051.21290@haegar.physiol.med.tu-muenchen.de>
1998-06-25  3:09         ` Performance measurements (thanks and conclusion) Martin Kahlert
1998-06-25  3:09 ` Performance measurements Jeffrey A Law
1998-06-26  1:05 ` Aubert Pierre
1998-06-27  2:25   ` Jeffrey A Law
1998-06-29 22:34 ` Rask Ingemann Lambertsen [this message]
1998-07-01  3:42   ` Nicholas Lee
1998-07-01 21:20 ` Marc Lehmann
1998-07-02  7:14   ` Craig Burley
1998-07-02 22:44     ` Marc Lehmann
1998-07-03  7:20       ` Toon Moene
1998-07-02 15:15   ` Joern Rennecke
1998-06-24 21:23 N8TM
1998-06-25  3:09 Christian Iseli
1998-06-25  6:50 Brad M. Garcia
1998-06-27 15:52 John Wehle

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=1748.484T1246T11154518@kampsax.k-net.dk \
    --to=rask@kampsax.k-net.dk \
    --cc=egcs@cygnus.com \
    /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).