public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Lehmann <pcg@goof.com>
To: egcs@cygnus.com
Subject: Re: Performance measurements
Date: Thu, 02 Jul 1998 22:44:00 -0000	[thread overview]
Message-ID: <19980702195628.31642@cerebro.laendle> (raw)
In-Reply-To: <199807021414.KAA28041@melange.gnu.org>

On Thu, Jul 02, 1998 at 10:14:27AM -0400, Craig Burley wrote:
> [Sorry I haven't tracked this thread; also I removed axp-list@redhat.com,
> since my comments apply to only the x86 processor.]

This is the code Martin Kahlert sent to egcs on 19980624.

> My guess, not knowing what the code is (even its language), is that

C. I've attached the code (slightly massaged to compile with glibc)

> this is due to the program being dependent mostly upon *static*

no, it uses auto variables *exclusively*.

> At least, that would explain the big difference in using
> -malign-double over -mno-align-double on 2.7.2.3, especially

unfortunately, it doesn.t

> Even if stack-based doubles are used a lot, whether the bad performance
> actually shows up in a benchmark can depend on fairly random things -- the
> "original case" reported to <fortran@gnu.org> being that the run-times
> differed *significantly* depending on the length of the *name* of the
> executable!!

I got a testcase written in C in early 1996! (three different matrix
multiply algorithms). This testcase resulted in the -mstack-align-double
switch of pgcc, and support for this in glibc and djgpp (not yet
distributed, though)

> At this point, with the 1.1 freeze looming, I feel we have too
> much more to learn about solving this problem right to try to
> rush a quick fix into 1.1.  Though, I'm going to try and keep
> it is a fairly top priority, to avoid having it slip until it's
> too late to fix properly (or at least decide we can't do so) in 1.2.

we need startup (libc) support. Bernd Schmidt once sent me a patch that
forced stack alignment in "main()", but I din't put this into pgcc, thinking
that isn't the right way to fix things.

At least for glibc, I could imagine having a switch for this (the proposed
-mstack-align-double) might help so the glibc people can put support
for it into glibc (i.e. compiling affected functions with that switch).

This would have the benefit of only forcing possible speed penalties on
functions with callbacks/startup functions.

      -----==-                                              |
      ----==-- _                                            |
      ---==---(_)__  __ ____  __       Marc Lehmann       +--
      --==---/ / _ \/ // /\ \/ /       pcg@goof.com       |e|
      -=====/_/_//_/\_,_/ /_/\_\                          --+
    The choice of a GNU generation                        |
                                                          |

  reply	other threads:[~1998-07-02 22:44 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
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 [this message]
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=19980702195628.31642@cerebro.laendle \
    --to=pcg@goof.com \
    --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).