From: "Yangfei (Felix)" <felix.yang@huawei.com>
To: Chenshanyao <chenshanyao@huawei.com>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Kugan <kugan.vivekanandarajah@linaro.org>
Subject: Re: [PATCH PR59593] [arm] Backport r217772 & r217826 to 4.8 & 4.9
Date: Sat, 29 Nov 2014 12:11:00 -0000 [thread overview]
Message-ID: <DA41BE1DDCA941489001C7FBD7A8820E837A2F03@szxema507-mbx.china.huawei.com> (raw)
In-Reply-To: <54796CD1.5040508@huawei.com>
> I've backported this fix to 4.8 & 4.9 branch.
> These patches have been tested for armeb-none-eabi-gcc/g++ with qemu, and
> both the test results were ok.
Looks OK with me. Ramana, is this OK for the 4.8 & 4.9 branches? Thanks.
next prev parent reply other threads:[~2014-11-29 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 7:12 [PATCH, PR63742][ARM] Fix arm *movhi_insn_arch4 pattern for big-endian Yangfei (Felix)
2014-11-05 11:01 ` Ramana Radhakrishnan
2014-11-06 8:36 ` Yangfei (Felix)
2014-11-18 8:54 ` Ramana Radhakrishnan
2014-11-18 11:36 ` Yangfei (Felix)
2014-11-18 12:04 ` Ramana Radhakrishnan
2014-11-18 12:47 ` Yangfei (Felix)
2014-11-18 12:56 ` Ramana Radhakrishnan
2014-11-19 9:42 ` Yangfei (Felix)
2014-11-19 10:26 ` Ramana Radhakrishnan
2014-11-20 9:24 ` Ramana Radhakrishnan
2014-11-20 9:25 ` Yangfei (Felix)
2014-11-20 9:48 ` Yangfei (Felix)
2014-11-29 10:58 ` [PATCH PR59593] [arm] Backport r217772 & r217826 to 4.8 & 4.9 Chen Shanyao
2014-11-29 12:11 ` Yangfei (Felix) [this message]
2014-12-02 12:22 ` Ramana Radhakrishnan
2014-11-12 10:28 ` [PING][PATCH, PR63742][ARM] Fix arm *movhi_insn_arch4 pattern for big-endian Yangfei (Felix)
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=DA41BE1DDCA941489001C7FBD7A8820E837A2F03@szxema507-mbx.china.huawei.com \
--to=felix.yang@huawei.com \
--cc=chenshanyao@huawei.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kugan.vivekanandarajah@linaro.org \
--cc=ramana.radhakrishnan@arm.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).