public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Aubert Pierre <paubert@laninsa.insa-lyon.fr>
Cc: Martin Kahlert <martin.kahlert@mchp.siemens.de>, egcs@cygnus.com
Subject: Re: Performance measurements
Date: Sat, 27 Jun 1998 02:25:00 -0000	[thread overview]
Message-ID: <5095.898928137@hurl.cygnus.com> (raw)
In-Reply-To: <wtk964u08r.fsf@laninsa.insa-lyon.fr>

  > Just for information, on HP
  > 
  > PA7200: gcc-2.7.2.2              -O3  :  26.63 MFLOPS
  > PA7200: egcs-2.91.42             -O3  :  47.13 MFLOPS
  > PA7200: cc                   -Ae +O4  :  52.88 MFLOPS
  > 
  > PA8000: gcc-2.7.2.2              -O3  : 108.31 MFLOPS
  > PA8000: egcs-2.91.42             -O3  :  97.10 MFLOPS
  > PA8000: cc            +DA1.1 -Ae +O4  : 129.47 MFLOPS 
  > PA8000: cc            +DA2.0 -Ae +O4  : 216.62 MFLOPS
  > 
  > egcs faster on PA8000 and slower on PA7200 than gcc-2.7.2.
  > cc is faster du to a better support of special instructions.
Err, you got that backwards :-)  egcs is faster than gcc2 on
the PA7200, but slower on the PA8000 series.

Note that you can get about a 30% improvement in this code on a
PA8000 by disabling the fmpyadd/fmpysub instructions.  They're
reorder buffer killers.

In fact, if someone wanted to submit a patch which added flags for
PA2.0 scheduling and codegen I'd accept it -- even if it did nothing
at this point.   Just having the flags allows us to start experimenting
with the code gen issues.

  > Is there a planed support for PA2.0 on HP?
I'd like to do it, but I don't have the time.  I'd happily accept
contributions.

Note first you have to add PA2.0 support in bfd/binutils/gas if
you're going to use any of the new instructions.

jeff

  reply	other threads:[~1998-06-27  2:25 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
1998-06-25  3:09 ` Jeffrey A Law
     [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-26  1:05 ` Performance measurements Aubert Pierre
1998-06-27  2:25   ` Jeffrey A Law [this message]
1998-06-29 22:34 ` Rask Ingemann Lambertsen
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=5095.898928137@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=martin.kahlert@mchp.siemens.de \
    --cc=paubert@laninsa.insa-lyon.fr \
    /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).