From: Xi Ruoyao <xry111@xry111.site>
To: chenglulu <chenglulu@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: Fix up memcpy-vec-3.c test case
Date: Sat, 09 Sep 2023 17:59:32 +0800 [thread overview]
Message-ID: <7386f2026866e909e5966f06d0083e8c9e3dcfec.camel@xry111.site> (raw)
In-Reply-To: <476c5661-e670-d0c8-7e29-9d339add0464@loongson.cn>
On Sat, 2023-09-09 at 16:21 +0800, chenglulu wrote:
> LGTM!
Pushed r14-3821.
> 在 2023/9/9 下午4:20, Xi Ruoyao 写道:
> > The generic code will split 16-byte copy into two 8-byte copies, so the
> > vector code wouldn't be used even if -mno-strict-align. This
> > contradicted with the purpose of this test case.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/loongarch/memcpy-vec-3.c: Increase the amount of
> > copied bytes to 32.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2023-09-09 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 8:20 Xi Ruoyao
2023-09-09 8:21 ` chenglulu
2023-09-09 9:59 ` Xi Ruoyao [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=7386f2026866e909e5966f06d0083e8c9e3dcfec.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--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).