From: Chen Gang <xili_gchen_5257@hotmail.com>
To: Bernd Schmidt <bernds@codesourcery.com>, Jeff Law <law@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] gcc/config/c6x/c6x.md: Remove "clobber (match_scratch ...)" in "movmisalign<mode>_store".
Date: Sat, 28 Mar 2015 06:24:00 -0000 [thread overview]
Message-ID: <BLU436-SMTP1838818C47DAD83C2C4DF37B9F70@phx.gbl> (raw)
In-Reply-To: <BLU436-SMTP209EC20DBDB9A57C5E27366B9F70@phx.gbl>
On 3/28/15 09:32, Chen Gang wrote:
> On 3/27/15 21:03, Bernd Schmidt wrote:
>> On 03/27/2015 01:05 AM, Chen Gang wrote:
>>> For misalignment memory access, c6x gcc will cause issue, so need remove
>>> "clobber (match_scratch ...)" which will be symmetric with "movmisalign
>>> <mode>_load", then pass compiling and generate correct assembly code.
>>>
>>
>>> * config/c6x/c6x.md (movmisalign<mode>_store): Remove "clobber
>>> (match_scratch ...)".
>>
>> No, that just will make the compiler confuse loads and stores. I've committed the following to fix it (I thought I'd done so a year ago, but probably it was one of those commit against an out-of-date tree situations and it didn't go through).
>>
>
> OK, thanks. Your patch is OK to me. And I shall try to find another c6x
> patches within this month (2015-03-31).
>
I have reported the related bug 65510, please continue for it, if I need
to continue, please let me know.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2015-03-28 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 0:05 Chen Gang
2015-03-27 0:18 ` Chen Gang
2015-03-27 13:04 ` Bernd Schmidt
2015-03-28 1:32 ` Chen Gang
2015-03-28 6:24 ` Chen Gang [this message]
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=BLU436-SMTP1838818C47DAD83C2C4DF37B9F70@phx.gbl \
--to=xili_gchen_5257@hotmail.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).