public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brad Lucier <lucier@math.purdue.edu>
To: jh@suse.cz (Jan Hubicka)
Cc: lucier@math.purdue.edu (Brad Lucier),
	gcc-patches@gcc.gnu.org, rth@cygnus.com, jh@suse.cz,
	gcc@gcc.gnu.org
Subject: Re: Timing information for CFG manipulations
Date: Tue, 16 Oct 2001 12:39:00 -0000	[thread overview]
Message-ID: <200110161939.f9GJdcb25102@banach.math.purdue.edu> (raw)
In-Reply-To: <20011016170137.D32633@atrey.karlin.mff.cuni.cz>

> 
> 
> Hi,
> this patch should track down the second problem:
> 
> >  flow 2                : 267.66 (34%) usr 251.44 (98%) sys 519.08 (49%) wall
> >  32.36    602.16   253.66     9556    26.54    26.54  sbitmap_vector_alloc
> 
> It makes find_sub_basic_blocks to operate at bitmap of blocks, instead of just
> one and thus it avoids multiple initializations of edge cache structure.
> 
> The possible problem is that I now need to benerate bitmap when calling from
> recog.c.  I hope it won't cause perofrmance regression as the bitmap is
> relativly small (compared to edge cache).  If it will, I can use bitmap,
> instead of sbitmap, that will add some overhead at split_all_insns side.
> 
> I don't have time to finish bootstrap, but the patch appears to work.
> OK assuming the bootstrapping/regtesting i386 passes fluently?

Bootstrapped and regtested on i686-pc-linux-gnu, flow2 is now

 flow 2                :  33.92 (16%) usr   0.10 ( 2%) sys  34.00 (16%) wall

So, two home runs in one day!  (Two goals in one day? ...)

Here are the new timing details:

Flat profile:

Each sample counts as 0.01 seconds.
  %   cumulative   self              self     total
 time   seconds   seconds    calls  ms/call  ms/call  name
 16.66     29.10    29.10 72698858     0.00     0.00  bitmap_operation
 12.43     50.81    21.71       13  1670.00  4145.64  calculate_global_regs_live
  9.86     68.04    17.23  9305997     0.00     0.00  cached_make_edge
  5.57     77.77     9.73    67331     0.14     0.38  try_crossjump_bb
  4.03     84.81     7.04                             htab_traverse
  2.99     90.03     5.22    27855     0.19     0.19  sbitmap_intersection_of_su
ccs

Brad

  reply	other threads:[~2001-10-16 12:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-13 20:33 Brad Lucier
2001-10-13 21:53 ` Zack Weinberg
2001-10-15 11:58   ` Brad Lucier
2001-10-16 21:15     ` Zack Weinberg
2001-10-15 12:54   ` Brad Lucier
2001-10-15 14:18     ` Daniel Berlin
2001-10-14  1:18 ` Jan Hubicka
2001-10-14  8:46   ` Brad Lucier
2001-10-14  9:21     ` Daniel Berlin
2001-10-16  7:22 ` Jan Hubicka
2001-10-16  8:25   ` Brad Lucier
2001-10-16 12:46   ` Richard Henderson
2001-10-16  8:01 ` Jan Hubicka
2001-10-16 12:39   ` Brad Lucier [this message]
2001-10-16 14:45     ` Jan Hubicka
2001-10-16 16:57       ` Brad Lucier
2001-10-17 12:43   ` Brad Lucier
2001-10-17 13:38   ` Richard Henderson
2001-10-17 14:00     ` Jan Hubicka
2001-10-17 15:38     ` Jan Hubicka
2001-10-17 16:10       ` Richard Henderson

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=200110161939.f9GJdcb25102@banach.math.purdue.edu \
    --to=lucier@math.purdue.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=rth@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).