public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Brad Lucier <lucier@math.purdue.edu>
Cc: jh@suse.cz, gcc@gcc.gnu.org
Subject: Re: Timing information for CFG manipulations
Date: Sat, 13 Oct 2001 21:53:00 -0000	[thread overview]
Message-ID: <20011013214715.S379@codesourcery.com> (raw)
In-Reply-To: <200110140332.f9E3W6I16651@banach.math.purdue.edu>

On Sat, Oct 13, 2001 at 10:32:06PM -0500, Brad Lucier wrote:
> Jan:
> 
> Here is timing information for today's CVS version of 3.1 configured
> with --enable-languages='c' --enable-checking=no and built with
> 'make bootstrap BOOT_CFLAGS="-O2 -g -pg" BOOT_LDFLAGS="-O2 -g -pg"'
> when called on the file at
> 
> http://www.math.purdue.edu/~lucier/_num.i.gz
...


>  44.47    348.50   348.50  7450804     0.05     0.05  remove_edge
>  32.36    602.16   253.66     9556    26.54    26.54  sbitmap_vector_alloc

...


>                 0.08    0.00       3/9556        flow_loops_find [59]
>                 0.16    0.00       6/9556        estimate_probability [33]
>                 0.16    0.00       6/9556        if_convert [25]
>                 0.32    0.00      12/9556        optimize_mode_switching [19]
>                 1.43    0.00      54/9556        pre_edge_lcm [24]
>               251.51    0.00    9475/9556        make_edges [10]
> [13]    32.4  253.66    0.00    9556         sbitmap_vector_alloc [13]

Two things:

- Can you repeat this test with cc1 linked against a profile-
instrumented libc, and libiberty re-built with CFLAGS="-O2 -g -pg"?
I'm suspicious that lots of time is being spent inside malloc.

- Have you tried Daniel Berlin's ebitmap patches?

zw

  reply	other threads:[~2001-10-13 21:53 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 [this message]
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
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=20011013214715.S379@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=lucier@math.purdue.edu \
    /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).