public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ssaupdate] Local dominance info
Date: Wed, 20 Oct 2004 22:26:00 -0000	[thread overview]
Message-ID: <1098310966.20227.24.camel@pain> (raw)
In-Reply-To: <20041020192719.GA20919@atrey.karlin.mff.cuni.cz>

On Wed, 2004-10-20 at 15:27, Zdenek Dvorak wrote:
> Hello,
> 
> > > this patch adds dominance information to statements, i.e. it makes it
> > > possible to decide whether a statement precedes other one inside a basic
> > > block without need to scan the whole block.
> > > 
> > > To enable this, statements inside basic block are numbered (the
> > > numbering contains holes, so that new statements may be inserted).  This
> > > seems to work good enough (no measurable impact on compile time).
> > 
> > You want to keep and maintain this information all the time?
> 
> yes.  Given that it costs nothing, it seems to be the best choice to me.
> 
> > This strikes me *much* more as a local thing that an individual pass
> > might be interested in, and so should number the stmt's itself for the
> > duration of its interest. 
> 
> Still you would need some mechanism to update things when statements are
> inserted, so this would make things only more complicated.

and what wrong with the local_dom_insert_after() and
local_dom_insert_before() which call the bsi routines? It looks pretty
trivial to do that,  then the info only exists and is maintained when
you want it.

I don't see any reason why it should be kept up to date all the time
when virtually no-one else cares about it. It seems like its a cheap to
calculate on the fly, and if its a big deal to you, then its not
difficult to keep up to date locally if you use local dominator aware
insert routines which call the BSI ones.

Andrew

  reply	other threads:[~2004-10-20 22:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 21:54 Zdenek Dvorak
2004-10-20 13:32 ` Andrew MacLeod
2004-10-20 19:35   ` Zdenek Dvorak
2004-10-20 22:26     ` Andrew MacLeod [this message]
2004-10-20 22:54       ` Zdenek Dvorak
2004-10-21  3:06         ` Jeffrey A Law
2004-10-22 16:38       ` Michael Matz
2004-10-22 17:05         ` Andrew MacLeod
2004-10-22 21:33           ` Zdenek Dvorak
2004-10-22 21:47             ` Andrew MacLeod
2004-10-21 10:25   ` Paolo Bonzini
2004-10-21 10:53     ` Zdenek Dvorak
2004-10-21 10:54       ` Paolo Bonzini

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=1098310966.20227.24.camel@pain \
    --to=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rakdver@atrey.karlin.mff.cuni.cz \
    /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).