From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] c++: Fix a typo in function name
Date: Tue, 15 Nov 2022 08:32:31 +0100 [thread overview]
Message-ID: <Y3NAj5CVTklLb8xg@tucnak> (raw)
Hi!
I've noticed I've made a typo in the name of the function.
Fixed thusly.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed
as obvious to trunk.
2022-11-15 Jakub Jelinek <jakub@redhat.com>
* cp-tree.h (next_common_initial_seqence): Rename to ...
(next_common_initial_sequence): ... this.
* typeck.cc (next_common_initial_seqence): Rename to ...
(next_common_initial_sequence): ... this.
(layout_compatible_type_p): Call next_common_initial_sequence
rather than next_common_initial_seqence.
* semantics.cc (is_corresponding_member_aggr): Likewise.
--- gcc/cp/cp-tree.h.jj 2022-11-14 13:35:34.311158621 +0100
+++ gcc/cp/cp-tree.h 2022-11-14 13:41:29.817322405 +0100
@@ -7982,7 +7982,7 @@ extern bool comp_except_specs (const_t
extern bool comptypes (tree, tree, int);
extern bool same_type_ignoring_top_level_qualifiers_p (tree, tree);
extern bool similar_type_p (tree, tree);
-extern bool next_common_initial_seqence (tree &, tree &);
+extern bool next_common_initial_sequence (tree &, tree &);
extern bool layout_compatible_type_p (tree, tree);
extern bool compparms (const_tree, const_tree);
extern int comp_cv_qualification (const_tree, const_tree);
--- gcc/cp/typeck.cc.jj 2022-11-14 13:35:34.474156404 +0100
+++ gcc/cp/typeck.cc 2022-11-14 13:42:07.328812124 +0100
@@ -1779,7 +1779,7 @@ similar_type_p (tree type1, tree type2)
the common initial sequence. */
bool
-next_common_initial_seqence (tree &memb1, tree &memb2)
+next_common_initial_sequence (tree &memb1, tree &memb2)
{
while (memb1)
{
@@ -1871,7 +1871,7 @@ layout_compatible_type_p (tree type1, tr
{
while (1)
{
- if (!next_common_initial_seqence (field1, field2))
+ if (!next_common_initial_sequence (field1, field2))
return false;
if (field1 == NULL_TREE)
return true;
--- gcc/cp/semantics.cc.jj 2022-11-14 13:35:34.429157016 +0100
+++ gcc/cp/semantics.cc 2022-11-14 13:41:47.930076022 +0100
@@ -11665,7 +11665,7 @@ is_corresponding_member_aggr (location_t
tree ret = boolean_false_node;
while (1)
{
- bool r = next_common_initial_seqence (field1, field2);
+ bool r = next_common_initial_sequence (field1, field2);
if (field1 == NULL_TREE || field2 == NULL_TREE)
break;
if (r
Jakub
reply other threads:[~2022-11-15 7:32 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=Y3NAj5CVTklLb8xg@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).