From: Diego Novillo <dnovillo@redhat.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] copy propagation and the abstraction penalty
Date: Thu, 15 May 2003 14:10:00 -0000 [thread overview]
Message-ID: <1053007822.4382.137.camel@frodo.toronto.redhat.com> (raw)
In-Reply-To: <20030514154455.A12416@synopsys.com>
On Wed, 2003-05-14 at 18:44, Joe Buck wrote:
> If we could do this alone, we would greatly improve C++ performance, especially
> on things like the Boost graph library. It seems that we have most of what we
> need in place, right?
>
There's a few bits still missing, but we should be getting there. In
this particular testcase I see:
* Structures. We only build enough SSA links to prove liveness.
Two alternatives to dealing with this is using ESSA from the
SSAPRE engine and/or rely on a scalarization pass.
* Aliasing. Our default type-based aliasing mechanism gets all
tangled up (it's really naive):
Alias information for complex addone(const complex&): 1 sets
Alias set #0:
Tag: *this, may aliases: *this, may alias global memory, call clobbered
Aliases objects: { <UV2150> *this <UV2770> *arg *b *this }
* The long term plan is to use PTA, which disambiguates this
program just fine. PTA still needs some work before we can
enable it by default. I'm also wondering if we could change the
may-alias between this and UV2150 to a must-alias, which would
completely free this program from aliasing problems:
Alias information for complex addone(const complex&): 1 sets
Alias set #0:
Tag: *this, may aliases: *this, .GLOBAL_VAR, call clobbered
Aliases objects: { <UV2150> *this }
Diego.
next prev parent reply other threads:[~2003-05-15 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 22:45 Joe Buck
2003-05-15 3:15 ` Andrew Pinski
2003-05-15 14:10 ` Diego Novillo [this message]
2003-05-15 17:09 ` Joe Buck
2003-05-15 17:28 ` Joe Buck
2003-05-15 18:01 ` Daniel Berlin
2003-05-15 22:20 ` Richard Henderson
2003-05-15 22:48 ` Joe Buck
2003-05-15 22:51 ` Joe Buck
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=1053007822.4382.137.camel@frodo.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.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).