public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
Cc: Matt Austern <austern@apple.com>, gcc@gcc.gnu.org
Subject: Re: Huge compile time & run time performance regression 3.3 -> HEAD
Date: Mon, 19 May 2003 21:04:00 -0000	[thread overview]
Message-ID: <m3fznaslb7.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0305192238330.464-100000@goofy>

Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> writes:

| > Do you see any compile time regressions at -O0?
| >
| > (I'm asking for the obvious reason: trying to find out how much work we
| > need to do in the front end as opposed to the back end.)
| 
| After killing all forced inlining, I get almost the same timings from 3.3
| and 3.4, namely 42.50 and 44.89 seconds.
| 
| Slowdown comes from
| 
| 3.3: name lookup           :   6.92 (17%) usr   0.90 (43%) sys   7.50
| (18%) wall
| 3.4: name lookup           :   9.06 (22%) usr   0.81 (39%) sys  10.29
| (23%) wall

I've also noticed that name lookup time has increased from 3.3 to 3.4,
probably mostly because now we're doing things more correctly and
partly because we didn't really take care to optimize it.  It would be
interesting if you could report numbers for name lookup for 3.4:

  * before I applied the name lookup
  * after I applied it (i.e. cvs as of this moment)

What I've noted (and I posted figures) wkas that the patch I applied
cut the name lookup time about half on mainline, whereas I got at
least 20%  on branch.

Thanks,

-- Gaby

  reply	other threads:[~2003-05-19 21:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 16:10 Richard Guenther
2003-05-18 19:22 ` Richard Guenther
2003-05-18 19:31   ` Richard Guenther
2003-05-18 19:35     ` Richard Guenther
2003-05-19 16:18 ` Matt Austern
2003-05-19 19:01   ` Richard Guenther
2003-05-19 20:51   ` Richard Guenther
2003-05-19 21:04     ` Gabriel Dos Reis [this message]
2003-05-19 21:10       ` Richard Guenther
2003-05-19 21:14         ` Gabriel Dos Reis
2003-05-19 21:24       ` Richard Guenther

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=m3fznaslb7.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=austern@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rguenth@tat.physik.uni-tuebingen.de \
    /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).