From: Tehila Meyzels <TEHILA@il.ibm.com>
To: Michael Matz <matz@suse.de>
Cc: Daniel Berlin <dberlin@dberlin.org>,
dpatel@apple.com, gcc@gcc.gnu.org,
gcc-patches@gcc.gnu.org, Revital1 Eres <ERES@il.ibm.com>,
trevor_smigiel@playstation.sony.com,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Victor Kaplansky <VICTORK@il.ibm.com>
Subject: Re: [RFC] Improve Tree-SSA if-conversion - convergence of efforts
Date: Mon, 06 Aug 2007 12:16:00 -0000 [thread overview]
Message-ID: <OF518A220D.E0270B9E-ONC225732F.0042D2FE-C225732F.004321C7@il.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707311701480.23011@wotan.suse.de>
Michael Matz <matz@suse.de> wrote on 31/07/2007 18:05:53:
> Hi,
>
> On Tue, 31 Jul 2007, Daniel Berlin wrote:
>
> > > 2. Store-sinking/load hoisting may have an overhead and may degrade
> > > performance unless the relevant conditional branch gets if-converted.
> >
> > I agree with you for conditional stores/loads.
> >
> > The unconditional store/load stuff, however, is exactly what
> > tree-ssa-sink was meant to do, and belongs there (this is #3 above).
I'm
> > certainly going to fight tooth and nail against trying to shoehorn
> > unconditional store sinking into if-conv.
>
> FWIW I also agree that handling unconditional stores/loads does not
belong
> in if-conv (or phi-opt), but in ssa-sink (or some similar transformation
> which can or can not use value numbers and the like).
OK.
And what's your opinion WRT conditional loads/stores?
Since you've sent your conditional store transformation patch,
I guess the meaning could be rewriting it on the top of tree-if-conv.
Tehila.
>
>
> Ciao,
> Michael.
next prev parent reply other threads:[~2007-08-06 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 14:51 Tehila Meyzels
2007-07-31 15:12 ` Daniel Berlin
2007-07-31 15:14 ` Michael Matz
2007-08-06 12:16 ` Tehila Meyzels [this message]
2007-08-06 14:31 ` Michael Matz
2007-08-01 11:02 ` Tehila Meyzels
2007-08-01 15:27 ` Daniel Berlin
2007-08-01 18:52 ` Ayal Zaks
2007-08-01 19:59 ` Daniel Berlin
2007-09-12 22:10 ` trevor_smigiel
2007-09-13 10:07 ` Richard Guenther
2007-09-13 10:55 ` Michael Matz
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=OF518A220D.E0270B9E-ONC225732F.0042D2FE-C225732F.004321C7@il.ibm.com \
--to=tehila@il.ibm.com \
--cc=ERES@il.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=VICTORK@il.ibm.com \
--cc=dberlin@dberlin.org \
--cc=dpatel@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
--cc=trevor_smigiel@playstation.sony.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).