From: Nick Alcock <nix@sourceware.org>
To: binutils-cvs@sourceware.org
Subject: [binutils-gdb] libctf: typos
Date: Fri, 17 May 2024 12:02:25 +0000 (GMT) [thread overview]
Message-ID: <20240517120225.8C2433858420@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7bc376bb9705cf66eea7b9a39442852b173ba6eb
commit 7bc376bb9705cf66eea7b9a39442852b173ba6eb
Author: Nick Alcock <nick.alcock@oracle.com>
Date: Fri Apr 26 17:50:20 2024 +0100
libctf: typos
Some functions were renamed without the comments catching up.
libctf/
* ctf-open.c (upgrade_types_v1): Fix comment typos.
Diff:
---
libctf/ctf-open.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libctf/ctf-open.c b/libctf/ctf-open.c
index 9cbf07626cc..03faf2d886f 100644
--- a/libctf/ctf-open.c
+++ b/libctf/ctf-open.c
@@ -438,7 +438,7 @@ upgrade_types_v1 (ctf_dict_t *fp, ctf_header_t *cth)
tbuf = (ctf_type_v1_t *) (fp->ctf_buf + cth->cth_typeoff);
tend = (ctf_type_v1_t *) (fp->ctf_buf + cth->cth_stroff);
- /* Much like init_types(), this is a two-pass process.
+ /* Much like init_static_types(), this is a two-pass process.
First, figure out the new type-section size needed. (It is possible,
in theory, for it to be less than the old size, but this is very
@@ -636,7 +636,7 @@ upgrade_types_v1 (ctf_dict_t *fp, ctf_header_t *cth)
/* Verify that the entire region was converted. If not, we are either
converting too much, or too little (leading to a buffer overrun either here
- or at read time, in init_types().) */
+ or at read time, in init_static_types().) */
assert ((size_t) t2p - (size_t) fp->ctf_buf == cth->cth_stroff);
reply other threads:[~2024-05-17 12:02 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=20240517120225.8C2433858420@sourceware.org \
--to=nix@sourceware.org \
--cc=binutils-cvs@sourceware.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).