From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] gimplify: Fix comment typos
Date: Tue, 25 Oct 2022 10:49:04 +0200 [thread overview]
Message-ID: <Y1ejAIVkd8y4CNJW@tucnak> (raw)
Hi!
While looking at gimple_boolify for PR107368, I've noticed 2 comment
typos.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2022-10-25 Jakub Jelinek <jakub@redhat.com>
* gimplify.cc (gimple_boolify): Fix comment typos, prduce -> produce
and There -> These.
--- gcc/gimplify.cc.jj 2022-10-24 11:01:54.121339779 +0200
+++ gcc/gimplify.cc 2022-10-24 11:21:44.215124376 +0200
@@ -4272,7 +4272,7 @@ gimple_boolify (tree expr)
default:
if (COMPARISON_CLASS_P (expr))
{
- /* There expressions always prduce boolean results. */
+ /* These expressions always produce boolean results. */
if (TREE_CODE (type) != BOOLEAN_TYPE)
TREE_TYPE (expr) = boolean_type_node;
return expr;
Jakub
reply other threads:[~2022-10-25 8:49 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=Y1ejAIVkd8y4CNJW@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).