From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] Spelling fix - cannott -> cannot [PR104899]
Date: Mon, 14 Mar 2022 10:42:47 +0100 [thread overview]
Message-ID: <Yi8OF8ByAUisgKmW@tucnak> (raw)
Hi!
This fixes typos and while changing that, also uses %< %> around attribute
names and fixes up formatting.
2022-03-14 Jakub Jelinek <jakub@redhat.com>
PR other/104899
* config/bfin/bfin.cc (bfin_handle_longcall_attribute): Fix a typo
in diagnostic message - cannott -> cannot. Use %< and %> around
names of attribute. Avoid too long line.
* range-op.cc (operator_logical_and::op1_range): Fix up a typo
in comment - cannott -> cannot. Use 2 spaces after . instead of one.
--- gcc/config/bfin/bfin.cc.jj 2022-02-04 14:36:54.301615132 +0100
+++ gcc/config/bfin/bfin.cc 2022-03-14 10:37:13.452701382 +0100
@@ -4763,7 +4763,8 @@ bfin_handle_longcall_attribute (tree *no
&& lookup_attribute ("longcall", TYPE_ATTRIBUTES (*node))))
{
warning (OPT_Wattributes,
- "cannott apply both longcall and shortcall attributes to the same function");
+ "cannot apply both %<longcall%> and %<shortcall%> attributes "
+ "to the same function");
*no_add_attrs = true;
}
--- gcc/range-op.cc.jj 2022-02-09 15:15:59.479837374 +0100
+++ gcc/range-op.cc 2022-03-14 10:38:07.038953734 +0100
@@ -2532,7 +2532,7 @@ operator_logical_and::op1_range (irange
break;
default:
// Any other result means only one side has to be false, the
- // other side can be anything. So we cannott be sure of any
+ // other side can be anything. So we cannot be sure of any
// result here.
r = range_true_and_false (type);
break;
Jakub
reply other threads:[~2022-03-14 9:42 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=Yi8OF8ByAUisgKmW@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).