From: Diego Novillo <dnovillo@redhat.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] Lazy updating of stmt operands
Date: Sun, 07 Dec 2003 17:14:00 -0000 [thread overview]
Message-ID: <1070816155.7334.13.camel@frodo.toronto.redhat.com> (raw)
In-Reply-To: <20031207161929.GA10638@atrey.karlin.mff.cuni.cz>
On Sun, 2003-12-07 at 11:19, Zdenek Dvorak wrote:
> what is the purpose of having lists of stmt operands updated on demand?
>
Performance. If the statement hasn't changed, no point re-scanning it.
> I thought that it is for performance reasons, but this seems not to be
> the case as all the statements are anyway scanned in the final dce pass,
> so they end up in updated forms and we cannot gain anything elsewhere.
>
The call to get_stmt_operands doesn't necessarily mean that the
statement will be re-scanned.
> Why I am interested in this is that it prevents us from having also
> def-use edges (immediate uses) provided explicitly, which would be
> convenient in two cases I have encountered recently.
>
tree-dfa.c:compute_immediate_uses()
Diego.
next prev parent reply other threads:[~2003-12-07 16:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 16:22 Zdenek Dvorak
2003-12-07 17:14 ` Diego Novillo [this message]
2003-12-07 17:28 ` Zdenek Dvorak
2003-12-07 17:36 ` Diego Novillo
2003-12-07 18:09 ` Zdenek Dvorak
2003-12-11 19:39 ` law
2003-12-07 22:20 ` Steven Bosscher
2003-12-09 14:30 ` Andrew MacLeod
2003-12-09 20:40 ` Zdenek Dvorak
2003-12-11 19:41 ` law
2003-12-11 19:38 ` law
2003-12-11 19:52 ` Zdenek Dvorak
2003-12-11 22:36 ` Zdenek Dvorak
2003-12-11 23:34 ` Andrew MacLeod
2003-12-15 19:10 ` Andrew MacLeod
2003-12-15 19:19 ` Zdenek Dvorak
2003-12-15 20:55 ` Andrew MacLeod
2003-12-15 21:06 ` Zdenek Dvorak
2003-12-15 21:39 ` Andrew MacLeod
2003-12-15 21:49 ` Zdenek Dvorak
2003-12-15 22:04 ` Andrew MacLeod
2003-12-15 22:39 ` law
2003-12-17 4:56 ` law
2003-12-16 23:32 ` Andrew MacLeod
2003-12-17 0:09 ` Zdenek Dvorak
2003-12-17 0:21 ` Andrew MacLeod
2003-12-17 3:28 ` law
2003-12-15 19:28 ` Diego Novillo
2003-12-11 22:31 Chris Lattner
2003-12-12 3:14 ` law
2003-12-12 3:58 ` Chris Lattner
2003-12-12 19:25 ` Andrew MacLeod
2003-12-12 19:42 ` Zdenek Dvorak
2003-12-12 19:45 ` Andrew MacLeod
2003-12-12 19:54 ` Chris Lattner
2003-12-12 19:55 ` Andrew MacLeod
2003-12-12 21:26 ` Diego Novillo
2003-12-12 19:57 ` Chris Lattner
2003-12-13 16:02 ` Andrew MacLeod
2003-12-14 3:39 ` Chris Lattner
2003-12-15 23:41 ` law
2003-12-16 6:02 ` Andrew MacLeod
2003-12-15 20:47 Chris Lattner
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=1070816155.7334.13.camel@frodo.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gcc@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).