From: James Greenhalgh <james.greenhalgh@arm.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Chung-Lin Tang <cltang@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: Re: [ARM] Fix build failure due to movsi_compare0 (PR 61430)
Date: Mon, 16 Jun 2014 09:55:00 -0000 [thread overview]
Message-ID: <20140616095528.GA24148@arm.com> (raw)
In-Reply-To: <539B2AF5.9010604@redhat.com>
On Fri, Jun 13, 2014 at 05:46:45PM +0100, Vladimir Makarov wrote:
> On 2014-06-11, 1:17 PM, Chung-Lin Tang wrote:
> > Looking at this too, as an LRA exercise. I don't really think the
> > pattern is wrong, rather LRA should just avoid creating the copy in this
> > case; it's a result of operand constraining, after all.
> >
> > Attached is the small LRA patch, pending testing. Vladimir should weight
> > in on this.
> >
>
> The patch is safe and ok. Thanks for working on it, Chung-Lin.
As this patch fixes a build failure on ARM I'd like to have it applied
today. If I don't hear anything which would stop me, I'll commit this on
Chung-Lin's behalf in a few hours.
Cheers,
James
>
> > * ira-lives.c (process_bb_lives): Skip creating copy during
> > insn sca when src/dest has constrained to same regno.
> >
>
>
next prev parent reply other threads:[~2014-06-16 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 10:32 [ARM] Fix build failure due to movsi_compare0 James Greenhalgh
2014-06-11 17:17 ` [ARM] Fix build failure due to movsi_compare0 (PR 61430) Chung-Lin Tang
2014-06-13 8:14 ` James Greenhalgh
2014-06-13 16:46 ` Vladimir Makarov
2014-06-16 9:55 ` James Greenhalgh [this message]
2014-06-16 10:00 ` Chung-Lin Tang
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=20140616095528.GA24148@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--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).