From: "Hale Wang" <hale.wang@arm.com>
To: "Segher Boessenkool" <segher@kernel.crashing.org>
Cc: <law@redhat.com>, "GCC Patches" <gcc-patches@gcc.gnu.org>,
"Richard Sandiford" <Richard.Sandiford@arm.com>,
"'Terry Guo'" <flameroc@gmail.com>
Subject: [PATCH] [gcc, combine] Backport to GCC 5.0 branch "PR46164: Don't combine the insns if a volatile register is contained".
Date: Thu, 14 May 2015 07:59:00 -0000 [thread overview]
Message-ID: <002d01d08e0a$cc6829a0$65387ce0$@arm.com> (raw)
> -----Original Message-----
> From: Terry Guo [mailto:flameroc@gmail.com]
> Sent: Wednesday, April 22, 2015 3:24 PM
> To: Segher Boessenkool
> Cc: law@redhat.com; Hale Wang; GCC Patches; Richard Sandiford
> Subject: Re: Ping^3 : [PATCH] [gcc, combine] PR46164: Don't combine the
> insns if a volatile register is contained.
>
> On Wed, Apr 22, 2015 at 10:30 AM, Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> > On Wed, Apr 22, 2015 at 10:21:43AM +0800, Terry Guo wrote:
> >> gcc/ChangeLog:
> >> 2015-04-22 Hale Wang <hale.wang@arm.com>
> >> Terry Guo <terry.guo@arm.com>
> >>
> >> PR rtl-optimization/64818
> >> * combine.c (can_combine_p): Don't combine user-specified register
> if
> >> it is in an asm input.
> >>
> >> gcc/testsuite/ChangeLog:
> >> 2015-04-22 Hale Wang <hale.wang@arm.com>
> >> Terry Guo <terry.guo@arm.com>
> >>
> >> PR rtl-optimization/64818
> >> * gcc.target/arm/pr64818.c: New.
> >
> > This is okay for trunk, if it has been bootstrapped and regression tested.
> >
> > Thanks,
> >
> >
> > Segher
>
> Thanks Segher. The patch is tested with bootstrap and regression test for
> x86_64. No problem found. Committed as revision 222306.
>
This patch applies cleanly on GCC 5.0 branch. Bootstrap and regression test are OK for X86_64.
Can we backport this patch to GCC 5.0 branch?
Best Regards,
Hale
> BR,
> Terry
next reply other threads:[~2015-05-14 5:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 7:59 Hale Wang [this message]
2015-05-14 13:36 ` Segher Boessenkool
2015-05-18 7:35 ` Hale Wang
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='002d01d08e0a$cc6829a0$65387ce0$@arm.com' \
--to=hale.wang@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=flameroc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.org \
/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).