From: Jeff Law <law@redhat.com>
To: Shiva Chen <shiva0217@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
gcc-patches@gcc.gnu.org
Subject: Re: ira.c update_equiv_regs patch causes gcc/testsuite/gcc.target/arm/pr43920-2.c regression
Date: Tue, 21 Apr 2015 05:27:00 -0000 [thread overview]
Message-ID: <5535DFB5.3020003@redhat.com> (raw)
In-Reply-To: <CAH=PD7a0ofWfFBnJqD=6e5uYJY8v_GRjcvRuOBvy-x3EZNzFJg@mail.gmail.com>
On 04/20/2015 01:09 AM, Shiva Chen wrote:
> Hi, Jeff
>
> Thanks for your advice.
>
> can_replace_by.patch is the new patch to handle both cases.
>
> pr43920-2.c.244r.jump2.ori is the original jump2 rtl dump
>
> pr43920-2.c.244r.jump2.patch_can_replace_by is the jump2 rtl dump
> after patch can_replace_by.patch
>
> Could you help me to review the patch?
Thanks. This looks pretty good.
I expanded the comment for the new function a bit and renamed the
function in an effort to clarify its purpose. From reviewing
can_replace_by, it seems it should have been handling this case, but
clearly wasn't due to implementation details.
I then bootstrapped and regression tested the patch on x86_64-linux-gnu
where it passed. I also instrumented that compiler to see how often
this code triggers. During a bootstrap it triggers a couple hundred
times (which is obviously a proxy for cross jumping improvements). So
it's triggering regularly on x86_64, which is good.
I also verified that this fixes BZ64916 for an arm-non-eabi toolchain
configured with --with-arch=armv7.
Installed on the trunk. No new testcase as it's covered by existing tests.
Thanks,,
jeff
next prev parent reply other threads:[~2015-04-21 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH=PD7Z2s3Yw+nWkhKBzEVrvg=aeBLhL-rZJQ=VtpgOjZZ+DLA@mail.gmail.com>
[not found] ` <55312EDF.90005@redhat.com>
2015-04-20 7:09 ` Shiva Chen
2015-04-21 5:27 ` Jeff Law [this message]
2015-07-28 18:55 ` Alex Velenko
2015-07-29 22:44 ` Jeff Law
2015-07-31 11:07 ` Alex Velenko
2015-08-18 9:36 ` Alex Velenko
2015-08-18 9:56 ` Marcus Shawcroft
2015-08-18 10:02 ` Alex Velenko
2015-08-18 10:05 ` Ramana Radhakrishnan
2015-08-18 13:30 ` Ramana Radhakrishnan
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=5535DFB5.3020003@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=shiva0217@gmail.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).