public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH][pushed] gcov: update documentation entry about string format
Date: Thu, 17 Jun 2021 11:39:47 +0200	[thread overview]
Message-ID: <3e4f2d65-b240-a6ea-0d0f-54551a075225@suse.cz> (raw)

gcc/ChangeLog:

	* gcov-io.h: Update documentation entry about string format.
---
  gcc/gcov-io.h | 7 +++----
  1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/gcc/gcov-io.h b/gcc/gcov-io.h
index f7584eb9679..ff92afe63df 100644
--- a/gcc/gcov-io.h
+++ b/gcc/gcov-io.h
@@ -42,15 +42,14 @@ see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
  
     Numbers are recorded in the 32 bit unsigned binary form of the
     endianness of the machine generating the file. 64 bit numbers are
-   stored as two 32 bit numbers, the low part first.  Strings are
-   padded with 1 to 4 NUL bytes, to bring the length up to a multiple
-   of 4. The number of 4 bytes is stored, followed by the padded
+   stored as two 32 bit numbers, the low part first.
+   The number of bytes is stored, followed by the
     string. Zero length and NULL strings are simply stored as a length
     of zero (they have no trailing NUL or padding).
  
     	int32:  byte3 byte2 byte1 byte0 | byte0 byte1 byte2 byte3
  	int64:  int32:low int32:high
-	string: int32:0 | int32:length char* char:0 padding
+	string: int32:0 | int32:length char* char:0
  	padding: | char:0 | char:0 char:0 | char:0 char:0 char:0
  	item: int32 | int64 | string
  
-- 
2.32.0


             reply	other threads:[~2021-06-17  9:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  9:39 Martin Liška [this message]
2021-06-21 19:27 Eugene Rozenfeld
2021-06-22  6:50 ` Martin Liška

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=3e4f2d65-b240-a6ea-0d0f-54551a075225@suse.cz \
    --to=mliska@suse.cz \
    --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).