From: Xionghu Luo <yinyuefengyi@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Fix typo
Date: Thu, 23 Jun 2022 11:01:08 +0800 [thread overview]
Message-ID: <20220623030108.3616432-1-xionghuluo@tencent.com> (raw)
Fix typo and commit as obvious.
Signed-off-by: Xionghu Luo <xionghuluo@tencent.com>
gcc/ChangeLog:
* cgraph.cc (cgraph_edge::redirect_call_stmt_to_callee): Fix
typo.
* tree-ssa-loop-ivopts.cc (struct iv_cand): Likewise.
* tree-switch-conversion.h: Likewise.
---
gcc/cgraph.cc | 2 +-
gcc/tree-ssa-loop-ivopts.cc | 2 +-
gcc/tree-switch-conversion.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/cgraph.cc b/gcc/cgraph.cc
index 7eeda53ca84..8d6ed38efa2 100644
--- a/gcc/cgraph.cc
+++ b/gcc/cgraph.cc
@@ -1423,7 +1423,7 @@ cgraph_edge::redirect_call_stmt_to_callee (cgraph_edge *e)
else
{
/* Be sure we redirect all speculative targets before poking
- abou tindirect edge. */
+ about indirect edge. */
gcc_checking_assert (e->callee);
cgraph_edge *indirect = e->speculative_call_indirect_edge ();
gcall *new_stmt;
diff --git a/gcc/tree-ssa-loop-ivopts.cc b/gcc/tree-ssa-loop-ivopts.cc
index 549168aebd6..a6f926a68ef 100644
--- a/gcc/tree-ssa-loop-ivopts.cc
+++ b/gcc/tree-ssa-loop-ivopts.cc
@@ -469,7 +469,7 @@ struct iv_cand
bitmap inv_vars; /* The list of invariant ssa_vars used in step of the
iv_cand. */
bitmap inv_exprs; /* If step is more complicated than a single ssa_var,
- hanlde it as a new invariant expression which will
+ handle it as a new invariant expression which will
be hoisted out of loop. */
struct iv *orig_iv; /* The original iv if this cand is added from biv with
smaller type. */
diff --git a/gcc/tree-switch-conversion.h b/gcc/tree-switch-conversion.h
index 2b677d9f7e9..4063a6c16a0 100644
--- a/gcc/tree-switch-conversion.h
+++ b/gcc/tree-switch-conversion.h
@@ -249,7 +249,7 @@ public:
/* Concrete subclass of group_cluster representing a collection
of cases to be implemented as a jump table.
- The "emit" vfunc gernerates a nested switch statement which
+ The "emit" vfunc generates a nested switch statement which
is later lowered to a jump table. */
class jump_table_cluster: public group_cluster
--
2.27.0
next reply other threads:[~2022-06-23 3:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 3:01 Xionghu Luo [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-24 11:20 Richard Biener
2015-11-03 14:16 Yulia Koval
2015-11-03 14:32 ` Uros Bizjak
2015-11-03 16:04 ` Yulia Koval
2015-05-10 21:01 Paulo Matos
2015-05-11 4:07 ` Jeff Law
2015-05-11 18:15 ` Paulo Matos
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=20220623030108.3616432-1-xionghuluo@tencent.com \
--to=yinyuefengyi@gmail.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).