From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Marat Zakirov <m.zakirov@samsung.com>,
Christophe Lyon <christophe.lyon@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Slava Garbuzov <v.garbuzov@samsung.com>,
Yury Gribov <y.gribov@samsung.com>
Subject: Re: [PING][PATCH] Fix for PR 61561
Date: Wed, 16 Jul 2014 09:36:00 -0000 [thread overview]
Message-ID: <53C646BB.6020905@arm.com> (raw)
In-Reply-To: <53C64468.9000506@samsung.com>
On 16/07/14 10:22, Marat Zakirov wrote:
> Christophe,
>
> Please look at a new patch. Draft tests are OK.
> I'll ask your commit approval when full regression (ARM/thumb1/thumb2)
> tests are done.
Hi Marat,
I was about to propose the thumb2.md hunk myself, but I'll defer to the
arm maintainers to comment on the other parts.
Also, in the ChangeLog it is helpful to specify which patterns are being
affected, so in your case it would be something like:
* config/arm/thumb1.md (*thumb1_movhi_insn): Handle stack pointer.
(*thumb1_movqi_insn): Likewise.
* config/arm/thumb2.md (*thumb2_movhi_insn): Ditto.
Kyrill
>
> Thank for your attention.
>
> --Marat
>
> On 07/11/2014 11:19 PM, Christophe Lyon wrote:
>> The new testcase causes an ICE when the compile is configured
>> --with-thumb or when forcing -mthumb.
>>
>> Christophe.
>>
>>
>> On 11 July 2014 11:08, Marat Zakirov <m.zakirov@samsung.com> wrote:
>>> Thank to you all.
>>>
>>> Committed revision 212450.
>>>
>>> --Marat
>>>
>>>
>>> -------- Original Message --------
>>> Subject: Re: [PING][PATCH] Fix for PR 61561
>>> Date: Thu, 10 Jul 2014 14:01:24 +0100
>>> From: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
>>> To: Marat Zakirov <m.zakirov@samsung.com>, "gcc-patches@gcc.gnu.org"
>>> <gcc-patches@gcc.gnu.org>
>>> CC: Richard Earnshaw <Richard.Earnshaw@arm.com>, Kyrylo Tkachov
>>> <Kyrylo.Tkachov@arm.com>, Slava Garbuzov <v.garbuzov@samsung.com>, Yuri
>>> Gribov <tetra2005@gmail.com>, "marat61@gmail.com" <marat61@gmail.com>
>>>
>>>
>>>
>>>
>>>
>>> On 30/06/14 16:21, Marat Zakirov wrote:
>>>> Thank for your attention.
>>> This is OK for trunk - Sorry about the delayed response.
>>>
>>> Ramana
>>>
>>>> Marat.
>>>>
>>>
next prev parent reply other threads:[~2014-07-16 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 15:21 Marat Zakirov
2014-07-10 12:57 ` [PING v2][PATCH] " Marat Zakirov
2014-07-10 13:01 ` [PING][PATCH] " Ramana Radhakrishnan
2014-07-11 9:09 ` Fwd: " Marat Zakirov
2014-07-11 19:19 ` Christophe Lyon
2014-07-14 7:45 ` Marat Zakirov
2014-07-14 9:07 ` Christophe Lyon
2014-07-16 9:24 ` Marat Zakirov
2014-07-16 9:36 ` Kyrill Tkachov [this message]
2014-07-17 12:18 ` Marat Zakirov
2014-07-23 13:47 ` Marat Zakirov
2014-07-30 13:07 ` [PINGv2][PATCH] " Marat Zakirov
2014-08-06 14:12 ` [PINGv3][PATCH] " Marat Zakirov
2014-08-06 14:14 ` Ramana Radhakrishnan
2014-08-06 14:44 ` Richard Earnshaw
2014-08-07 7:37 ` Marat Zakirov
2014-08-07 8:01 ` Ramana Radhakrishnan
2014-08-07 8:11 ` Marat Zakirov
2014-08-07 8:50 ` Richard Earnshaw
2014-08-07 9:02 ` Marat Zakirov
2014-08-07 13:52 ` Marat Zakirov
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=53C646BB.6020905@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=m.zakirov@samsung.com \
--cc=v.garbuzov@samsung.com \
--cc=y.gribov@samsung.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).