diff mbox series

gcov-io.h: fix comment regarding length of records

Message ID 87il6w9ora.fsf@oracle.com
State Accepted
Headers
Series gcov-io.h: fix comment regarding length of records |

Checks

Context Check Description
snail/gcc-patch-check success Github commit url

Commit Message

Jose E. Marchesi Oct. 24, 2023, 12:41 p.m. UTC 
  The length of gcov records is stored as a signed 32-bit number of bytes.
Ok?

Comments

Jeff Law Oct. 24, 2023, 6:02 p.m. UTC | #1 
On 10/24/23 06:41, Jose E. Marchesi wrote:
> 
> The length of gcov records is stored as a signed 32-bit number of bytes.
> Ok?
OK.
jeff
Jose E. Marchesi Oct. 24, 2023, 7:10 p.m. UTC | #2 
> On 10/24/23 06:41, Jose E. Marchesi wrote:
>> The length of gcov records is stored as a signed 32-bit number of
>> bytes.
>> Ok?
> OK.

Pushed.  Thanks.
diff mbox series

Patch

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