public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-7445] strlen: Comment spelling fixes
Date: Wed,  2 Mar 2022 09:26:58 +0000 (GMT)	[thread overview]
Message-ID: <20220302092658.6F2203858D39@sourceware.org> (raw)

https://gcc.gnu.org/g:31702fe9694e7ebeab91805e7121a1a757c108bd

commit r12-7445-g31702fe9694e7ebeab91805e7121a1a757c108bd
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Mar 2 10:26:27 2022 +0100

    strlen: Comment spelling fixes
    
    This fixes some comment spelling bugs in tree-ssa-strlen.cc.
    
    2022-03-02  Jakub Jelinek  <jakub@redhat.com>
    
            * tree-ssa-strlen.cc (strlen_pass::handle_assign,
            strlen_pass::before_dom_children): Comment spelling fixes.

Diff:
---
 gcc/tree-ssa-strlen.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/tree-ssa-strlen.cc b/gcc/tree-ssa-strlen.cc
index 7370516da45..112f0dce874 100644
--- a/gcc/tree-ssa-strlen.cc
+++ b/gcc/tree-ssa-strlen.cc
@@ -5573,7 +5573,7 @@ strlen_pass::handle_integral_assign (bool *cleanup_eh)
 }
 
 /* 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_block bb)
   /* 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))


                 reply	other threads:[~2022-03-02  9:26 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=20220302092658.6F2203858D39@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@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).