From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] strlen: Comment spelling fixes
Date: Wed, 2 Mar 2022 10:29:34 +0100 [thread overview]
Message-ID: <Yh84/lQqWyYcM0i2@tucnak> (raw)
Hi!
This fixes some comment spelling bugs in tree-ssa-strlen.cc.
Committed as obvious.
2022-03-02 Jakub Jelinek <jakub@redhat.com>
* tree-ssa-strlen.cc (strlen_pass::handle_assign,
strlen_pass::before_dom_children): Comment spelling fixes.
--- gcc/tree-ssa-strlen.cc.jj 2022-02-04 14:36:56.341586640 +0100
+++ gcc/tree-ssa-strlen.cc 2022-03-01 13:55:08.645284651 +0100
@@ -5573,7 +5573,7 @@ strlen_pass::handle_integral_assign (boo
}
/* Handle assignment statement at *GSI to LHS. Set *ZERO_WRITE if
- the assignent stores all zero bytes.. */
+ the assignment stores all zero bytes. */
bool
strlen_pass::handle_assign (tree lhs, bool *zero_write)
@@ -5811,7 +5811,7 @@ strlen_pass::before_dom_children (basic_
/* Attempt to optimize individual statements. */
for (m_gsi = gsi_start_bb (bb); !gsi_end_p (m_gsi); )
{
- /* Reset search depth preformance counter. */
+ /* Reset search depth performance counter. */
ptr_qry.depth = 0;
if (check_and_optimize_stmt (&cleanup_eh))
Jakub
reply other threads:[~2022-03-02 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Yh84/lQqWyYcM0i2@tucnak \
--to=jakub@redhat.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).