From: Jeffrey A Law <law@cygnus.com>
To: Michael Matz <matzmich@cs.tu-berlin.de>
Cc: Brad Lucier <lucier@math.purdue.edu>,
Richard Henderson <rth@cygnus.com>,
gcc@gcc.gnu.org
Subject: Re: if-conversion a performance bottleneck
Date: Fri, 05 May 2000 12:01:00 -0000 [thread overview]
Message-ID: <5423.957553224@upchuck> (raw)
In-Reply-To: <Pine.SOL.4.10.10005030741450.1121-200000@platon>
In message < Pine.SOL.4.10.10005030741450.1121-200000@platon >you write:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
> Send mail to mime@docserver.cac.washington.edu for more info.
>
> ---559023410-33463914-957333180=:1121
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hi,
>
> On Tue, 2 May 2000, Michael Matz wrote:
> > > time seconds seconds calls ms/call ms/call name
> > > 57.51 111.67 111.67 40604 2.75 2.75 sbitmap_intersection_of_succs
> > > 12.83 136.59 24.92 15025 1.66 1.66 sbitmap_intersection_of_preds
> >
> > I once had faster versions of these two functions, if I get home I'll see
> > if they make any difference on your input data.
>
> Before fiddling with sbitmap_intersection_of_xx() I first reworked
> compute_flow_dominators() to also behave normally in calculating the
> post_doms. At least the order of work-queue initialization was wrong (in
> post_dom the changes are propagating from the _end_). I then also
> implemented a poor man's topological sort for cyclic graphs ;), which
> again gave a better performance. (I also did this once for doms, but there
> it didn't make a great difference on Brads test cases)
>
> Please try the attached diff (against actual CVS) if they make also a
> difference for you ;)
Like Richard, I'd like to see you submit this as a function which can be
called from multiple locations in the compiler.
We've got a number of routines that _might_ benefit from this code, but
I'd also like to see some more general benchmarking. I don't want to
see us slow down the compiler for the common cases just to make Brad's
one test run faster.
jeff
next prev parent reply other threads:[~2000-05-05 12:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-01 10:54 Brad Lucier
2000-05-01 15:29 ` Richard Henderson
2000-05-01 18:01 ` Brad Lucier
2000-05-02 5:45 ` Michael Matz
2000-05-02 22:58 ` Michael Matz
2000-05-03 5:50 ` Brad Lucier
2000-05-03 20:05 ` Brad Lucier
2000-05-04 11:46 ` Michael Matz
2000-05-04 19:39 ` Brad Lucier
2000-05-04 22:16 ` Richard Henderson
2000-05-10 8:30 ` Andreas Schwab
2000-05-10 9:36 ` Joe Buck
2000-05-10 9:52 ` Jeffrey A Law
2000-05-10 10:49 ` Joe Buck
2000-05-10 14:17 ` Joern Rennecke
2000-05-10 14:24 ` GNU make options (was Re: if-conversion ...) Joe Buck
2000-05-04 11:55 ` if-conversion a performance bottleneck Richard Henderson
2000-05-05 12:01 ` Jeffrey A Law [this message]
2000-05-05 14:32 ` flow_d_f_o_compute misnamed? (was: if-conversion a performance...) Michael Matz
2000-05-05 14:53 ` Jeffrey A Law
2000-05-05 16:10 ` Michael Matz
2000-05-05 17:05 ` Jeffrey A Law
2000-05-05 18:21 ` Michael Matz
2000-05-05 19:04 ` Michael Hayes
2000-05-11 17:14 ` Jeffrey A Law
2000-05-04 22:32 if-conversion a performance bottleneck Mike Stump
2000-05-04 22:35 ` Richard Henderson
2000-05-05 6:12 ` Brad Lucier
2000-05-05 10:37 ` Richard Henderson
2000-05-05 13:35 ` Gerald Pfeifer
2000-05-04 23:28 Mathias Froehlich
2000-05-05 13:46 Brad Lucier
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=5423.957553224@upchuck \
--to=law@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=lucier@math.purdue.edu \
--cc=matzmich@cs.tu-berlin.de \
--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).