public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: chenglulu <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: Chenghui Pan <panchenghui@loongson.cn>,
	i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: Use LSX and LASX for block move
Date: Sat, 9 Sep 2023 15:14:17 +0800	[thread overview]
Message-ID: <0140721c-9281-a832-2874-04230af24698@loongson.cn> (raw)
In-Reply-To: <f366ab1e287fe9d6fc7f95df4d8ecce1b166b4a9.camel@xry111.site>


在 2023/9/9 下午3:06, Xi Ruoyao 写道:
> On Sat, 2023-09-09 at 15:04 +0800, chenglulu wrote:
>> Hi,RuoYao:
>>
>>    I think the test example memcpy-vec-3.c submitted in r14-3818 is
>> implemented incorrectly.
>>
>> The 16-byte length in this test example will cause can_move_by_pieces to
>> return true when with '-mstrict-align', so no vector load instructions
>> will be generated.
> Yes, in this case we cannot use vst because we don't know if b is
> aligned.  Thus a { scan-assembler-not "vst" } guarantees that.
>
> Or am I understanding something wrongly here?
>
Well, what I mean is that even if '-mno-strict-align' is used here, 
vst/vld will not be used,

so this test example cannot test what we want to test.


  reply	other threads:[~2023-09-09  7:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 16:14 Xi Ruoyao
2023-09-09  6:10 ` chenglulu
2023-09-09  7:03   ` Pushed: [PATCH v2] " Xi Ruoyao
2023-09-09  7:04 ` [PATCH] " chenglulu
2023-09-09  7:06   ` Xi Ruoyao
2023-09-09  7:14     ` chenglulu [this message]
2023-09-09  7:15       ` Xi Ruoyao

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=0140721c-9281-a832-2874-04230af24698@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=panchenghui@loongson.cn \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).