From: "Sinan" <sinan.lin@linux.alibaba.com>
To: "gcc-patches" <gcc-patches@gcc.gnu.org>
Subject: [PATCH] Fix doc typo
Date: Wed, 09 Nov 2022 11:28:25 +0800 [thread overview]
Message-ID: <9b8f291f-277c-40ce-8b94-ad0eeff7dfe5.sinan.lin@linux.alibaba.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 29 bytes --]
add a missing variable name.
[-- Attachment #2: 0001-doc-FixDocTypo.patch --]
[-- Type: application/octet-stream, Size: 360 bytes --]
diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi
index f962ef9b1ee..38bae981736 100644
--- a/gcc/doc/tree-ssa.texi
+++ b/gcc/doc/tree-ssa.texi
@@ -227,7 +227,7 @@ all the operands for a statement:
void
print_ops (tree stmt)
@{
- ssa_op_iter;
+ ssa_op_iter iter;
tree var;
FOR_EACH_SSA_TREE_OPERAND (var, stmt, iter, SSA_OP_ALL_OPERANDS)
next reply other threads:[~2022-11-09 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 3:28 Sinan [this message]
2022-11-09 7:51 ` Richard Biener
2022-11-09 20:58 ` Martin Liška
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=9b8f291f-277c-40ce-8b94-ad0eeff7dfe5.sinan.lin@linux.alibaba.com \
--to=sinan.lin@linux.alibaba.com \
--cc=gcc-patches@gcc.gnu.org \
/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).