From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rguenther <rguenther@suse.de>,
Tamar.Christina <Tamar.Christina@arm.com>,
richard.sandiford <richard.sandiford@arm.com>
Subject: middle-end: Support early break/return auto-vectorization.
Date: Mon, 15 May 2023 13:20:20 +0800 [thread overview]
Message-ID: <1B90F6E28150AE2F+2023051513201989155653@rivai.ai> (raw)
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
Hi, this patch is very interesting patch and I found it's very beneficial after applying to my downstream RVV GCC.
However, it has been a long time that this patch didn't update.
Is it possible that this patch will be refined and merged into trunk in the future ?
Thanks
juzhe.zhong@rivai.ai
next reply other threads:[~2023-05-15 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 5:20 juzhe.zhong [this message]
2023-05-15 13:16 ` Tamar Christina
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=1B90F6E28150AE2F+2023051513201989155653@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=Tamar.Christina@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--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).