public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] tree-switch-conversion: Fix a comment typo
Date: Wed, 19 Jul 2023 13:53:59 +0200	[thread overview]
Message-ID: <ZLfO1++M5xx11xF5@tucnak> (raw)

Hi!

I've noticed a comment typo, this patch fixes that.

Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk
as obvious.

2023-07-19  Jakub Jelinek  <jakub@redhat.com>

	* tree-switch-conversion.h (class bit_test_cluster): Fix comment typo.

--- gcc/tree-switch-conversion.h.jj	2023-02-17 12:45:08.218636117 +0100
+++ gcc/tree-switch-conversion.h	2023-07-18 10:10:21.398933379 +0200
@@ -303,7 +303,7 @@ public:
 /* A GIMPLE switch statement can be expanded to a short sequence of bit-wise
 comparisons.  "switch(x)" is converted into "if ((1 << (x-MINVAL)) & CST)"
 where CST and MINVAL are integer constants.  This is better than a series
-of compare-and-banch insns in some cases,  e.g. we can implement:
+of compare-and-branch insns in some cases,  e.g. we can implement:
 
 	if ((x==4) || (x==6) || (x==9) || (x==11))
 

	Jakub


                 reply	other threads:[~2023-07-19 11:54 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=ZLfO1++M5xx11xF5@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).