From: "Paulo J. Matos" <paulo@matos-sorge.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>, gcc@gcc.gnu.org
Subject: Re: Move insn out of the way
Date: Fri, 12 Aug 2011 10:01:00 -0000 [thread overview]
Message-ID: <CAKQyQBff+0NtD2K-_C0XT8nmb+=eXYA6gTf6R=9FdsS4R3YACg@mail.gmail.com> (raw)
In-Reply-To: <4E43E6BC.90003@redhat.com>
On Thu, Aug 11, 2011 at 3:27 PM, Vladimir Makarov <vmakarov@redhat.com> wrote:
> Yes, that is mostly correct. The first could be done by -fweb (if the live
> range where the pseudo is equal to the constant is disjoint). The first
> could be done also by Jeff Law's project which can provide splitting not
> only on the border of loops.
>
I was thinking that one possible solution in the short term would be
to add a new pass just before IRA which does constant assignment
moves. So, an insn where a register which is assigned a constant can
be moved as much as possible to the place right before the use of the
register or if there's no use of the register inside the current BB,
it can be moved as the last instruction of the BB.
What do you think about this? Would this work? I know it's not very
general, however, it's useful at least for my backend to get this
right as soon as possible due to several size test failures we have
which are a consequence of this problem.
Paulo Matos
next prev parent reply other threads:[~2011-08-12 10:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 11:20 Paulo J. Matos
2011-08-10 11:40 ` Richard Guenther
2011-08-10 11:42 ` Richard Guenther
2011-08-10 13:55 ` Paulo J. Matos
[not found] ` <4E431BD8.8060705@redhat.com>
2011-08-11 8:12 ` Paulo J. Matos
2011-08-11 8:49 ` Richard Guenther
2011-08-11 14:27 ` Vladimir Makarov
2011-08-12 10:01 ` Paulo J. Matos [this message]
2011-08-12 14:22 ` Vladimir Makarov
2011-08-12 15:06 ` Paulo J. Matos
2011-08-12 16:12 ` Jeff Law
2011-08-11 12:22 ` Paulo J. Matos
2011-08-10 13:46 ` Paulo J. Matos
2011-08-10 13:51 ` Richard Guenther
2011-08-10 14:14 ` Paulo J. Matos
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='CAKQyQBff+0NtD2K-_C0XT8nmb+=eXYA6gTf6R=9FdsS4R3YACg@mail.gmail.com' \
--to=paulo@matos-sorge.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=vmakarov@redhat.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).