From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] tree-ssa-tail-merge: Fix a comment typo
Date: Tue, 5 Sep 2023 09:35:57 +0200 [thread overview]
Message-ID: <ZPbaXTuV2ARYl4ew@tucnak> (raw)
Hi!
I've noticed a typo in a comment, fixed thusly.
Committed to trunk as obvious.
2023-09-05 Jakub Jelinek <jakub@redhat.com>
* tree-ssa-tail-merge.cc (replace_block_by): Fix a comment typo:
avreage -> average.
--- gcc/tree-ssa-tail-merge.cc.jj 2023-07-11 13:40:40.253431941 +0200
+++ gcc/tree-ssa-tail-merge.cc 2023-09-04 22:46:50.035269079 +0200
@@ -1605,7 +1605,7 @@ replace_block_by (basic_block bb1, basic
/* If probabilities are same, we are done.
If counts are nonzero we can distribute accordingly. In remaining
- cases just avreage the values and hope for the best. */
+ cases just average the values and hope for the best. */
e2->probability = e1->probability.combine_with_count
(bb1->count, e2->probability, bb2->count);
}
Jakub
reply other threads:[~2023-09-05 7:36 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=ZPbaXTuV2ARYl4ew@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).