public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: gcc@gcc.gnu.org
Subject: Re: Huge compile time & run time performance regression 3.3 -> HEAD
Date: Sun, 18 May 2003 19:22:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0305182052150.457-100000@goofy> (raw)
In-Reply-To: <Pine.LNX.4.44.0305181734000.457-100000@goofy>

On Sun, 18 May 2003, Richard Guenther wrote:

> Hi!
>
> As 3.3 is now out, I start comparing 3.3 to HEAD wrt compile time
> performance and performance of the resulting code. As always these
> comparisons are for a POOMA based scientific application.
>
> I experience a 100% compile time regression (673.50s -> 1284.48s) and
> a 12% runtime performance regression (150s -> 171s) when comparing
> gcc3.3 to HEAD.
>
> Time reports follow, the most prominent regressions are expand, global CSE
> (>300%!), loop analysis and branch prediction.

Top of a profile of gcc3.4 is

Flat profile:

Each sample counts as 0.01 seconds.
  %   cumulative   self              self     total
 time   seconds   seconds    calls   s/call   s/call  name
  7.47     79.18    79.18      906     0.09     0.09  compute_store_table
  6.92    152.54    73.36 262785751     0.00     0.00  expr_equiv_p
  6.76    224.21    71.67   170098     0.00     0.00  fixup_var_refs_insns
  5.58    283.38    59.17    12865     0.00     0.00  loop_regs_scan
  4.39    329.97    46.59   364279     0.00     0.00  compute_transp
  4.10    373.46    43.49 308470718     0.00     0.00
splay_tree_splay_helper
  3.27    408.15    34.69 201411415     0.00     0.00  fixup_var_refs_1
  3.02    440.22    32.07 192083288     0.00     0.00  true_dependence
  2.88    470.76    30.54 232168274     0.00     0.00
mems_in_disjoint_alias_sets_p
  2.39    496.11    25.35    10203     0.00     0.00  loop_regs_update
  2.36    521.17    25.06      686     0.04     0.04  build_store_vectors
  2.00    542.36    21.19  3266323     0.00     0.00
invalid_mode_change_p
  1.95    563.04    20.68   374046     0.00     0.00  alloc_page
  1.86    582.79    19.75 180849685     0.00     0.00  find_loads
  1.47    598.39    15.60   214475     0.00     0.00  ldst_entry
  1.28    611.95    13.56  4111368     0.00     0.00
gt_ggc_mx_lang_tree_node
  1.04    622.99    11.04 201411428     0.00     0.00  fixup_var_refs_insn
  1.03    633.94    10.95      906     0.01     0.01  store_motion
  1.03    644.86    10.92    18177     0.00     0.00  fixup_var_refs
  1.01    655.57    10.71 1468353297     0.00     0.00
splay_tree_compare_ints
  1.00    666.14    10.57 15850095     0.00     0.00  walk_tree

full profile can be fetched from

http:://www.tat.physik.uni-tuebingen.de/~rguenth/gcc/profile_34.gz

Richard.

  reply	other threads:[~2003-05-18 18:54 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 [this message]
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
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=Pine.LNX.4.44.0305182052150.457-100000@goofy \
    --to=rguenth@tat.physik.uni-tuebingen.de \
    --cc=gcc@gcc.gnu.org \
    /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).