From: "Lehua Ding" <lehua.ding@rivai.ai>
To: rguenther <rguenther@suse.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"richard.sandiford" <richard.sandiford@arm.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Subject: Re: Re: [PATCH V2] VECT: Support floating-point in-order reduction for length loop control
Date: Sun, 23 Jul 2023 12:32:14 +0800 [thread overview]
Message-ID: <D5CA799EF3F960E2+tencent_368C12F24C7DCDAE29A7875DD287D3F5F406@qq.com> (raw)
In-Reply-To: <F93C584F25CDDF58+2023072119080415873746@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Hi Richard,
Bootstrap and regression are passed on X86 and
no new testcases fail on AArch64 with V5 patch:
https://gcc.gnu.org/pipermail/gcc-patches/2023-July/625293.html
V5 patch is ok for trunk?
Best,
Lehua
next prev parent reply other threads:[~2023-07-23 4:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 10:05 juzhe.zhong
2023-07-21 10:51 ` Richard Biener
2023-07-21 10:59 ` juzhe.zhong
2023-07-21 11:08 ` juzhe.zhong
2023-07-23 4:32 ` Lehua Ding [this message]
2023-07-24 6:44 ` Richard Biener
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=D5CA799EF3F960E2+tencent_368C12F24C7DCDAE29A7875DD287D3F5F406@qq.com \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.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).