From: Richard Sandiford <richard.sandiford@arm.com>
To: "juzhe.zhong\@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: rguenther <rguenther@suse.de>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] VECT: Support CALL vectorization for COND_LEN_*
Date: Tue, 25 Jul 2023 11:21:00 +0100 [thread overview]
Message-ID: <mptmszkfg1f.fsf@arm.com> (raw)
In-Reply-To: <04ABFAE5A832E860+2023072518172420282933@rivai.ai> (juzhe's message of "Tue, 25 Jul 2023 18:17:24 +0800")
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai> writes:
> Thanks Richard.
>
> Do you suggest we should add a macro like this first:
>
> #ifndef DEF_INTERNAL_COND_FN
> #define DEF_INTERNAL_COND_FN(NAME, FLAGS, OPTAB, TYPE) \
> DEF_INTERNAL_OPTAB_FN (COND_##NAME, FLAGS, cond_##optab, cond_##TYPE)
> DEF_INTERNAL_OPTAB_FN (COND_LEN_##NAME, FLAGS, cond_len_##optab, cond_len_##TYPE)
> #endif
Yeah. (Think there's a missing backslash though.)
> If yes, maybe I should first do this in a single patch first?
Yeah, doing it as a separate patch sounds good.
Richard
next prev parent reply other threads:[~2023-07-25 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 11:46 juzhe.zhong
2023-07-24 14:33 ` Richard Biener
2023-07-24 23:16 ` 钟居哲
2023-07-25 9:41 ` Richard Sandiford
2023-07-25 10:17 ` juzhe.zhong
2023-07-25 10:21 ` Richard Sandiford [this message]
2023-07-25 11:31 ` juzhe.zhong
2023-07-25 12:18 ` Richard Sandiford
2023-07-31 9:30 ` 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=mptmszkfg1f.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=rguenther@suse.de \
/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).