From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] Fix comment typos
Date: Wed, 17 Jan 2024 11:23:01 +0100 [thread overview]
Message-ID: <Zaeqhb6NFEtVi3im@tucnak> (raw)
Hi!
When looking at PR113410, I found a comment typo and just searched for
the same typo elsewhere and found some typos in the comments which had
that typo as well.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to
trunk as obvious.
2024-01-17 Jakub Jelinek <jakub@redhat.com>
* tree-into-ssa.cc (pass_build_ssa::gate): Fix comment typo,
funcions -> functions, and use were instead of was.
* gengtype.cc (dump_typekind): Fix comment typos, funcion -> function
and guaranteee -> guarantee.
* attribs.h (struct attr_access): Fix comment typo funcion -> function.
--- gcc/tree-into-ssa.cc.jj 2024-01-03 11:51:34.128695146 +0100
+++ gcc/tree-into-ssa.cc 2024-01-16 18:57:38.136438943 +0100
@@ -2499,7 +2499,7 @@ public:
/* opt_pass methods: */
bool gate (function *fun) final override
{
- /* Do nothing for funcions that was produced already in SSA form. */
+ /* Do nothing for functions that were produced already in SSA form. */
return !(fun->curr_properties & PROP_ssa);
}
--- gcc/gengtype.cc.jj 2024-01-03 11:51:23.314845233 +0100
+++ gcc/gengtype.cc 2024-01-16 18:56:57.383009291 +0100
@@ -4718,8 +4718,8 @@ write_roots (pair_p variables, bool emit
}
/* Prints not-as-ugly version of a typename of T to OF. Trades the uniquness
- guaranteee for somewhat increased readability. If name conflicts do happen,
- this funcion will have to be adjusted to be more like
+ guarantee for somewhat increased readability. If name conflicts do happen,
+ this function will have to be adjusted to be more like
output_mangled_typename. */
#define INDENT 2
--- gcc/attribs.h.jj 2024-01-03 11:51:24.200832936 +0100
+++ gcc/attribs.h 2024-01-16 19:08:27.507350364 +0100
@@ -324,7 +324,7 @@ struct attr_access
in TREE_VALUE and their positions in the argument list (stored
in TREE_PURPOSE). Each expression may be a PARM_DECL or some
other DECL (for ordinary variables), or an EXPR for other
- expressions (e.g., funcion calls). */
+ expressions (e.g., function calls). */
tree size;
/* The zero-based position of each of the formal function arguments.
Jakub
next reply other threads:[~2024-01-17 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 10:23 Jakub Jelinek [this message]
2024-01-19 21:14 ` rep.dot.nop
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 7:11 Jakub Jelinek
2022-10-07 11:21 ` Jonathan Wakely
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=Zaeqhb6NFEtVi3im@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).