public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tehila Meyzels <TEHILA@il.ibm.com>
To: "Daniel Berlin" <dberlin@dberlin.org>
Cc: dpatel@gmail.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
	        "Michael Matz" <matz@suse.de>,
	Revital1 Eres <ERES@il.ibm.com>,
	        trevor_smigiel@playstation.sony.com,
	        "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>,
	        Victor Kaplansky <VICTORK@il.ibm.com>,
	Ayal Zaks <ZAKS@il.ibm.com>,
	        Dorit Nuzman <DORIT@il.ibm.com>
Subject: Re: [RFC] Improve Tree-SSA if-conversion - convergence of efforts
Date: Wed, 01 Aug 2007 11:02:00 -0000	[thread overview]
Message-ID: <OF6D5C42EB.60221AE4-ONC225732A.0027ACC6-C225732A.003C5B48@il.ibm.com> (raw)
In-Reply-To: <4aca3dc20707310800j41fb5cel4ef815bbad42be07@mail.gmail.com>

"Daniel Berlin" <dberlin@dberlin.org> wrote on 31/07/2007 18:00:57:

>
> I agree with you for conditional stores/loads.

Great!

>
> 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.

Sometimes, store-sinking can cause performance degradations.
One reason for that, is increasing register pressure, due to extending life
range of registers.

In addition, in case we have a store followed by a branch, store sinking
result will be a branch followed by a store.
On some architectures, the former can be executed in parallel, as opposed
to the latter.
Thus, in this case, it worth executing store-sinking only when it helps the
if-conversion to get rid of the branch.

How do you suggest to solve this problem, in case store-sinking will be
part of the tree-sink pass?

Another point, what about (unconditional) load hoisting:
It's surely not related to sink pass, right?

Tehila.

  parent reply	other threads:[~2007-08-01 11:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 13:46 Tehila Meyzels
2007-07-31 15:01 ` Daniel Berlin
2007-07-31 15:06   ` Michael Matz
2007-08-06 12:16     ` Tehila Meyzels
2007-08-06 14:31       ` Michael Matz
2007-08-01 11:02   ` Tehila Meyzels [this message]
2007-08-01 15:27     ` Daniel Berlin
2007-08-01 18:52       ` Ayal Zaks
2007-08-01 19:59         ` Daniel Berlin
2007-09-12 21:48 ` trevor_smigiel
2007-09-13  9:24   ` Richard Guenther
2007-09-13  9:58   ` 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=OF6D5C42EB.60221AE4-ONC225732A.0027ACC6-C225732A.003C5B48@il.ibm.com \
    --to=tehila@il.ibm.com \
    --cc=DORIT@il.ibm.com \
    --cc=ERES@il.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=VICTORK@il.ibm.com \
    --cc=ZAKS@il.ibm.com \
    --cc=dberlin@dberlin.org \
    --cc=dpatel@gmail.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).