public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/8361] [3.3/3.4/4.0 regression] C++ compile-time performance regression
Date: Fri, 12 Nov 2004 12:52:00 -0000	[thread overview]
Message-ID: <20041112125224.20648.qmail@sourceware.org> (raw)
In-Reply-To: <20021025133601.8361.gerald@pfeifer.com>


------- Additional Comments From steven at gcc dot gnu dot org  2004-11-12 12:52 -------
GCC 3.4 (CVS today) takes 35s usr on my machine.
GCC 4.0 (CVS today) takes 46s usr on the same machine.

The difference is entirely in DOM, into-SSA and SSA-other
which is really also into-SSA:

			usr	sys	wall
dominator optimization	3.16	0.02	3.26
tree SSA rewrite	3.24	0.01	3.27
tree SSA other		3.47	0.09	3.40


Per-pass and cummulative time spent (top 10 only):
integration             1.09    2.30%   48.88%
tree PHI insertion      1.21    2.56%   51.44%
loop invariant motion   1.30    2.75%   54.18%
global alloc            1.30    2.75%   56.93%
CSE                     1.72    3.63%   60.56%
parser                  3.05    6.44%   67.00%
dominator optimization  3.16    6.68%   73.68%
tree SSA rewrite        3.24    6.84%   80.52%
tree SSA other          3.47    7.33%   87.85%
expand                  5.75    12.15%  100.00%


Flat profile:
                                                                               
                
Each sample counts as 0.01 seconds.
  %   cumulative   self              self     total
 time   seconds   seconds    calls   s/call   s/call  name
  1.82      8.19     8.19 13878865     0.00     0.00  is_gimple_reg
  1.50     14.95     6.76     6594     0.00     0.00  synth_mult
  1.28     20.69     5.74 12785589     0.00     0.00  ggc_alloc_stat
  1.27     26.38     5.69  3433257     0.00     0.00  free_df_for_stmt
  1.25     32.01     5.63 16868123     0.00     0.00  bitmap_set_bit
  1.19     37.35     5.34  4846931     0.00     0.00  get_stmt_operands
  1.17     42.59     5.24    62034     0.00     0.00  alloc_page
  1.15     47.75     5.16     3559     0.00     0.01  compute_immediate_uses
  0.99     52.18     4.43  6408238     0.00     0.00  htab_find_slot_with_hash
  0.98     56.60     4.42  2104725     0.00     0.00  compute_immediate_uses_for_phi
  0.93     60.76     4.16   821051     0.00     0.00  gt_ggc_mx_lang_tree_node
  0.91     64.83     4.07  7802758     0.00     0.00  register_new_def
  0.90     68.87     4.04   951728     0.00     0.00  rewrite_stmt
  0.88     72.82     3.95 30035694     0.00     0.00  bitmap_bit_p
  0.84     76.61     3.79   574332     0.00     0.00  cse_insn
  0.81     80.26     3.65   196671     0.00     0.00  compute_global_livein
  0.81     83.91     3.65   177070     0.00     0.00  insert_phi_nodes_for
  0.81     87.54     3.63  2697441     0.00     0.00  for_each_rtx
  0.81     91.16     3.62  1079773     0.00     0.00  check_phi_redundancy

which is a different way of saying "all over the map" :-(



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8361


  parent reply	other threads:[~2004-11-12 12:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021025133601.8361.gerald@pfeifer.com>
2003-10-16  2:39 ` [Bug optimization/8361] [3.3/3.4 " mmitchel at gcc dot gnu dot org
2003-12-29 16:23 ` steven at gcc dot gnu dot org
2004-01-02  2:31 ` giovannibajo at libero dot it
2004-01-14  3:22 ` pinskia at gcc dot gnu dot org
2004-01-21 18:28 ` [Bug optimization/8361] [3.3/3.4/3.5 " gerald at pfeifer dot com
2004-02-06  1:44 ` pinskia at gcc dot gnu dot org
2004-03-13 16:38 ` mmitchel at gcc dot gnu dot org
2004-06-18 23:39 ` [Bug rtl-optimization/8361] " mmitchel at gcc dot gnu dot org
2004-06-22  8:38 ` gerald at pfeifer dot com
2004-06-25  4:32 ` pinskia at gcc dot gnu dot org
2004-06-25  7:44 ` pinskia at gcc dot gnu dot org
2004-08-29 18:50 ` mmitchel at gcc dot gnu dot org
2004-09-15 10:13 ` [Bug rtl-optimization/8361] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org
2004-09-18 14:40 ` pinskia at gcc dot gnu dot org
2004-09-24 15:01 ` bonzini at gcc dot gnu dot org
2004-10-26 12:34 ` nathan at gcc dot gnu dot org
2004-10-26 13:34 ` gerald at pfeifer dot com
2004-10-26 13:37 ` pinskia at gcc dot gnu dot org
2004-10-30 19:30 ` mmitchel at gcc dot gnu dot org
2004-11-12 12:52 ` steven at gcc dot gnu dot org [this message]
2004-11-18 18:56 ` pinskia at gcc dot gnu dot org
2004-11-19 18:22 ` pinskia at gcc dot gnu dot org
2004-12-04 16:31 ` pinskia at gcc dot gnu dot org
2004-12-18  4:13 ` pinskia at gcc dot gnu dot org
2004-12-23 11:16 ` steven at gcc dot gnu dot org
2005-01-10  1:35 ` pinskia at gcc dot gnu dot org
2005-01-16  4:50 ` pinskia at gcc dot gnu dot org
2005-01-16 14:16 ` belyshev at depni dot sinp dot msu dot ru
2005-01-16 14:21 ` steven at gcc dot gnu dot org
2005-01-28 14:48 ` pinskia at gcc dot gnu dot org
2005-01-28 15:15 ` steven at gcc dot gnu dot org
2005-02-06 15:34 ` steven@gcc.gnu.org
2005-02-06 16:26 ` steven@gcc.gnu.org
2005-02-06 16:54 ` steven@gcc.gnu.org
2005-02-07  2:13 ` ghazi at gcc dot gnu dot org
2005-02-08 10:19 ` gerald at pfeifer dot com
2005-07-23 22:14 ` [Bug rtl-optimization/8361] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-09-18 19:17 ` pinskia at gcc dot gnu dot org
2005-09-18 19:27 ` pinskia at gcc dot gnu dot org

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=20041112125224.20648.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).