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-8131] scev: Fix a comment typo
Date: Wed, 13 Apr 2022 07:48:20 +0000 (GMT)	[thread overview]
Message-ID: <20220413074820.6B6393858025@sourceware.org> (raw)

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

commit r12-8131-gccb5e638370cd228032d5a8c0ca343c46caaa4b4
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Apr 13 09:47:45 2022 +0200

    scev: Fix a comment typo
    
    When looking at the kernel __popcountdi2 issue, I've noticed a comment typo.
    
    2022-04-13  Jakub Jelinek  <jakub@redhat.com>
    
            * tree-scalar-evolution.cc (expression_expensive_p): Fix a comment typo.

Diff:
---
 gcc/tree-scalar-evolution.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/tree-scalar-evolution.cc b/gcc/tree-scalar-evolution.cc
index 61d72c278a1..44157265ce8 100644
--- a/gcc/tree-scalar-evolution.cc
+++ b/gcc/tree-scalar-evolution.cc
@@ -3395,7 +3395,7 @@ expression_expensive_p (tree expr, hash_map<tree, uint64_t> &cache,
       call_expr_arg_iterator iter;
       /* Even though is_inexpensive_builtin might say true, we will get a
 	 library call for popcount when backend does not have an instruction
-	 to do so.  We consider this to be expenseive and generate
+	 to do so.  We consider this to be expensive and generate
 	 __builtin_popcount only when backend defines it.  */
       combined_fn cfn = get_call_combined_fn (expr);
       switch (cfn)


                 reply	other threads:[~2022-04-13  7:48 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=20220413074820.6B6393858025@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).