public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chen Gang <xili_gchen_5257@hotmail.com>
To: Jeff Law <law@redhat.com>, bernds@codesourcery.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: Fri, 27 Mar 2015 00:18:00 -0000	[thread overview]
Message-ID: <BLU436-SMTP430AA53E5FAD24391601CEB9090@phx.gbl> (raw)
In-Reply-To: <BLU436-SMTP54E724354B094F919100DB9090@phx.gbl>



On 3/27/15 08:05, 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.
> 
> The related issue:
> 
>   [root@localhost c6x]# cat test.i
>   int oxu_driver_init(void)
>   {
>    *(volatile unsigned int *)(-1) = *(unsigned int *)(-1);

Oh, sorry, I use 11 instead of -1 for generating the assembly code (-1
and 11 lead the same result).

[...]

>   oxu_driver_init:
>                 mvk     .d1     11, A4
>                 ldnw    .d1t1   *A4, A3
>                 nop     4
>                 stnw    .d1t1   A3, *A4
>                 ret     .s2     B3
>                 nop     5
>         .size   oxu_driver_init, .-oxu_driver_init
>         .ident  "GCC: (GNU) 5.0.0 20150321 (experimental)"
> 
[...]

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2015-03-27  0:18 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 [this message]
2015-03-27 13:04 ` Bernd Schmidt
2015-03-28  1:32   ` Chen Gang
2015-03-28  6:24     ` Chen Gang

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-SMTP430AA53E5FAD24391601CEB9090@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).