From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ssaupdate] Local dominance info
Date: Wed, 20 Oct 2004 19:35:00 -0000 [thread overview]
Message-ID: <20041020192719.GA20919@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <1098279112.5695.3918.camel@pain>
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.
Zdenek
next prev parent reply other threads:[~2004-10-20 19:27 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 [this message]
2004-10-20 22:26 ` Andrew MacLeod
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=20041020192719.GA20919@atrey.karlin.mff.cuni.cz \
--to=rakdver@atrey.karlin.mff.cuni.cz \
--cc=amacleod@redhat.com \
--cc=gcc-patches@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).