public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-4894] gcc: fix typo in comment in gcov-io.h
@ 2023-10-24 19:08 Jose E. Marchesi
0 siblings, 0 replies; only message in thread
From: Jose E. Marchesi @ 2023-10-24 19:08 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:e6fdea823eb7053f2fc5d752824710213f8e3f54
commit r14-4894-ge6fdea823eb7053f2fc5d752824710213f8e3f54
Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Date: Tue Oct 24 21:07:12 2023 +0200
gcc: fix typo in comment in gcov-io.h
gcc/ChangeLog:
* gcov-io.h: Fix record length encoding in comment.
Diff:
---
gcc/gcov-io.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/gcov-io.h b/gcc/gcov-io.h
index bfe4439d02d..e6f33e32652 100644
--- a/gcc/gcov-io.h
+++ b/gcc/gcov-io.h
@@ -101,7 +101,7 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If not, see
Records are not nested, but there is a record hierarchy. Tag
numbers reflect this hierarchy. Tags are unique across note and
data files. Some record types have a varying amount of data. The
- LENGTH is the number of 4bytes that follow and is usually used to
+ LENGTH is the number of bytes that follow and is usually used to
determine how much data. The tag value is split into 4 8-bit
fields, one for each of four possible levels. The most significant
is allocated first. Unused levels are zero. Active levels are
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-10-24 19:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-24 19:08 [gcc r14-4894] gcc: fix typo in comment in gcov-io.h Jose E. Marchesi
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).