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 r13-519] forwprop: Fix a typo and comment formatting
Date: Tue, 17 May 2022 07:08:07 +0000 (GMT)	[thread overview]
Message-ID: <20220517070807.A01923858C74@sourceware.org> (raw)

https://gcc.gnu.org/g:bc9aa450eb47e440a4b909a10a271fe074e896eb

commit r13-519-gbc9aa450eb47e440a4b909a10a271fe074e896eb
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue May 17 09:06:55 2022 +0200

    forwprop: Fix a typo and comment formatting
    
    When looking around the spot of the PR105591 fix, I've noticed a typo
    and incorrectly formatted comment.
    
    2022-05-17  Jakub Jelinek  <jakub@redhat.com>
    
            * tree-ssa-forwprop.cc (simplify_bitfield_ref): Spelling fix:
            hanlde -> handle.  Fix up comment formatting.

Diff:
---
 gcc/tree-ssa-forwprop.cc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/gcc/tree-ssa-forwprop.cc b/gcc/tree-ssa-forwprop.cc
index 7da3f80af10..0917202b74c 100644
--- a/gcc/tree-ssa-forwprop.cc
+++ b/gcc/tree-ssa-forwprop.cc
@@ -2356,14 +2356,14 @@ simplify_bitfield_ref (gimple_stmt_iterator *gsi)
   code = gimple_assign_rhs_code (def_stmt);
   elem_type = TREE_TYPE (TREE_TYPE (op0));
   type = TREE_TYPE (op);
-  /* Also hanlde vector type.
-   .i.e.
-   _7 = VEC_PERM_EXPR <_1, _1, { 2, 3, 2, 3 }>;
-   _11 = BIT_FIELD_REF <_7, 64, 0>;
+  /* Also handle vector type.
+     .i.e.
+     _7 = VEC_PERM_EXPR <_1, _1, { 2, 3, 2, 3 }>;
+     _11 = BIT_FIELD_REF <_7, 64, 0>;
 
-   to
+     to
 
-   _11 = BIT_FIELD_REF <_1, 64, 64>.  */
+     _11 = BIT_FIELD_REF <_1, 64, 64>.  */
 
   size = tree_to_poly_uint64 (TYPE_SIZE (type));
   if (maybe_ne (bit_field_size (op), size))


                 reply	other threads:[~2022-05-17  7:08 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=20220517070807.A01923858C74@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).