public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4049] c++: Fix a typo in function name Date: Tue, 15 Nov 2022 07:18:46 +0000 (GMT) [thread overview] Message-ID: <20221115071846.4A29D3830B29@sourceware.org> (raw) https://gcc.gnu.org/g:87c4057b3fc7fe2c2f8914d2755024ca890a3bc1 commit r13-4049-g87c4057b3fc7fe2c2f8914d2755024ca890a3bc1 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Nov 15 08:17:11 2022 +0100 c++: Fix a typo in function name I've noticed I've made a typo in the name of the function. Fixed thusly. 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. Diff: --- gcc/cp/cp-tree.h | 2 +- gcc/cp/semantics.cc | 2 +- gcc/cp/typeck.cc | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/gcc/cp/cp-tree.h b/gcc/cp/cp-tree.h index bbc8be21900..5e4f4d81180 100644 --- a/gcc/cp/cp-tree.h +++ b/gcc/cp/cp-tree.h @@ -7982,7 +7982,7 @@ extern bool comp_except_specs (const_tree, const_tree, int); 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); diff --git a/gcc/cp/semantics.cc b/gcc/cp/semantics.cc index 3c37d75bee6..b1917496cb3 100644 --- a/gcc/cp/semantics.cc +++ b/gcc/cp/semantics.cc @@ -11665,7 +11665,7 @@ is_corresponding_member_aggr (location_t loc, tree basetype1, tree membertype1, 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 diff --git a/gcc/cp/typeck.cc b/gcc/cp/typeck.cc index 5f5fb2a212b..55c958533b4 100644 --- a/gcc/cp/typeck.cc +++ b/gcc/cp/typeck.cc @@ -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, tree type2) { while (1) { - if (!next_common_initial_seqence (field1, field2)) + if (!next_common_initial_sequence (field1, field2)) return false; if (field1 == NULL_TREE) return true;
reply other threads:[~2022-11-15 7:18 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=20221115071846.4A29D3830B29@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).