public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: law@redhat.com
To: Diego Novillo <dnovillo@redhat.com>
Cc: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] Lazy updating of stmt operands
Date: Thu, 11 Dec 2003 19:38:00 -0000	[thread overview]
Message-ID: <200312111936.hBBJabGj024859@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Sun, 07 Dec 2003 12:29:46 EST." <1070818186.7334.30.camel@frodo.toronto.redhat.com>

In message <1070818186.7334.30.camel@frodo.toronto.redhat.com>, Diego Novillo w
rites:
 >> > tree-dfa.c:compute_immediate_uses()
 >> 
 >> Which needs to pass through every single statement in the program. Not
 >> really terribly efficient.
 >> 
 >*shrug*, it's used by SSA-CCP.  Since def-use edges are only needed by
 >some passes, I don't think it would be worth our while trying to
 >maintain them in get_stmt_operands.
 >
 >But I'm ready to be convinced otherwise.  Say, with an implementation
 >comparing both approaches with timings over a reasonable code base (a
 >typical GCC bootstrap or one of the compile-time related PRs).
IMHO, when we have the need, then we'll expand on the immediate uses
interface -- either by having a way to incrementally update it, or 
rebuild it.

While it's nice to think about a world where you always have immediate uses,
you end up with FUD chains if you do that -- with ultimately a tangled nest
of pointers that is bloody impossible to work with in the real world.

jeff

  parent reply	other threads:[~2003-12-11 19:36 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
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 [this message]
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=200312111936.hBBJabGj024859@speedy.slc.redhat.com \
    --to=law@redhat.com \
    --cc=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).