From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] Fix comment typos
Date: Fri, 7 Oct 2022 12:21:51 +0100 [thread overview]
Message-ID: <Y0ALz3UdNOjof7g1@redhat.com> (raw)
In-Reply-To: <Yz/REPRnQs0T2CXz@tucnak>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On 07/10/22 09:11 +0200, Jakub Jelinek wrote:
>--- gcc/ipa-prop.h.jj 2022-05-25 11:07:29.516188277 +0200
>+++ gcc/ipa-prop.h 2022-10-06 16:12:52.157055672 +0200
>@@ -78,7 +78,7 @@ struct ipa_cst_ref_desc;
> /* Structure holding data required to describe a constant jump function. */
> struct GTY(()) ipa_constant_data
> {
>- /* THe value of the constant. */
>+ /* The value of the constant. */
> tree value;
> /* Pointer to the structure that describes the reference. */
> struct ipa_cst_ref_desc GTY((skip)) *rdesc;
>--- gcc/value-range.cc.jj 2022-10-06 08:55:02.668291942 +0200
>+++ gcc/value-range.cc 2022-10-06 16:12:17.161531334 +0200
>@@ -2508,7 +2508,7 @@ irange::irange_contains_p (const irange
> // Otherwise, check if this's pair occurs before R's.
> if (wi::lt_p (wi::to_wide (u), wi::to_wide (rl), sign))
> {
>- // THere's still at leats one pair of R left.
>+ // There's still at leats one pair of R left.
There's still at least one typo here ;-)
I'll push the attached as obvious.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 771 bytes --]
commit 5c868666ce2014acf64d817dc31031deab1ecc93
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Oct 7 12:20:36 2022
gcc: Fix comment typo
gcc/ChangeLog:
* value-range.cc (irange::irange_contains_p): Fix comment typo.
diff --git a/gcc/value-range.cc b/gcc/value-range.cc
index 16105f87678..a14f9bc4394 100644
--- a/gcc/value-range.cc
+++ b/gcc/value-range.cc
@@ -2509,7 +2509,7 @@ irange::irange_contains_p (const irange &r) const
// Otherwise, check if this's pair occurs before R's.
if (wi::lt_p (wi::to_wide (u), wi::to_wide (rl), sign))
{
- // There's still at leats one pair of R left.
+ // There's still at least one pair of R left.
if (++i >= num_pairs ())
return false;
l = m_base[i * 2];
next prev parent reply other threads:[~2022-10-07 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 7:11 Jakub Jelinek
2022-10-07 11:21 ` Jonathan Wakely [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 10:23 Jakub Jelinek
2024-01-19 21:14 ` rep.dot.nop
2007-11-14 13:10 Rask Ingemann Lambertsen
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=Y0ALz3UdNOjof7g1@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).