From: Juzhe-Zhong <juzhe.zhong@rivai.ai>
To: gcc-patches@gcc.gnu.org
Cc: richard.sandiford@arm.com, rguenther@suse.de,
Juzhe-Zhong <juzhe.zhong@rivai.ai>
Subject: [PATCH V2] DOC: Update COND_LEN document
Date: Thu, 26 Oct 2023 17:53:46 +0800 [thread overview]
Message-ID: <20231026095346.3190168-1-juzhe.zhong@rivai.ai> (raw)
gcc/ChangeLog:
* doc/md.texi: Adapt COND_LEN pseudo code.
---
gcc/doc/md.texi | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index daa318ee3da..fab2513105a 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -7341,8 +7341,10 @@ store the result in operand 0, otherwise store operand 2 in operand 0.
The operation only works for the operands are vectors.
@smallexample
-for (i = 0; i < ops[4] + ops[5]; i++)
- op0[i] = op1[i] ? @var{op} op2[i] : op3[i];
+for (i = 0; i < GET_MODE_NUNITS (@var{m}); i++)
+ op0[i] = (i < ops[4] + ops[5] && op1[i]
+ ? @var{op} op2[i]
+ : op3[i]);
@end smallexample
where, for example, @var{op} is @code{~} for @samp{cond_len_one_cmpl@var{mode}}.
@@ -7403,8 +7405,10 @@ store the result in operand 0, otherwise store operand 4 in operand 0.
The operation only works for the operands are vectors.
@smallexample
-for (i = 0; i < ops[5] + ops[6]; i++)
- op0[i] = op1[i] ? op2[i] @var{op} op3[i] : op4[i];
+for (i = 0; i < GET_MODE_NUNITS (@var{m}); i++)
+ op0[i] = (i < ops[5] + ops[6] && op1[i]
+ ? op2[i] @var{op} op3[i]
+ : op4[i]);
@end smallexample
where, for example, @var{op} is @code{+} for @samp{cond_len_add@var{mode}}.
@@ -7436,8 +7440,10 @@ takes 3 operands rather than two. For example, the vector form of
@samp{cond_len_fma@var{mode}} is equivalent to:
@smallexample
-for (i = 0; i < ops[6] + ops[7]; i++)
- op0[i] = op1[i] ? fma (op2[i], op3[i], op4[i]) : op5[i];
+for (i = 0; i < GET_MODE_NUNITS (@var{m}); i++)
+ op0[i] = (i < ops[6] + ops[7] && op1[i]
+ ? fma (op2[i], op3[i], op4[i])
+ : op5[i]);
@end smallexample
@cindex @code{neg@var{mode}cc} instruction pattern
--
2.36.3
next reply other threads:[~2023-10-26 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 9:53 Juzhe-Zhong [this message]
2023-10-26 9:56 ` Richard Sandiford
2023-10-26 10:01 ` juzhe.zhong
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=20231026095346.3190168-1-juzhe.zhong@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--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).