public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1111] DOC: Update __gcov_dump documentation.
Date: Fri, 28 May 2021 11:38:28 +0000 (GMT)	[thread overview]
Message-ID: <20210528113828.73B743857804@sourceware.org> (raw)

https://gcc.gnu.org/g:d2a913c76f41692fd0bb955d1768f462133d813a

commit r12-1111-gd2a913c76f41692fd0bb955d1768f462133d813a
Author: Martin Liska <mliska@suse.cz>
Date:   Fri May 28 13:35:33 2021 +0200

    DOC: Update __gcov_dump documentation.
    
            PR gcov-profile/100751
    
    gcc/ChangeLog:
    
            * doc/gcov.texi: Revert partially a hunk that was wrong.

Diff:
---
 gcc/doc/gcov.texi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/gcc/doc/gcov.texi b/gcc/doc/gcov.texi
index d076721b93c..32b51f984bc 100644
--- a/gcc/doc/gcov.texi
+++ b/gcc/doc/gcov.texi
@@ -887,8 +887,7 @@ Long-running applications can use the @code{__gcov_reset} and @code{__gcov_dump}
 facilities to restrict profile collection to the program region of
 interest. Calling @code{__gcov_reset(void)} will clear all run-time profile
 counters to zero, and calling @code{__gcov_dump(void)} will cause the profile
-information collected at that point to be dumped to @file{.gcda} output files
-(the function can be called just once).
+information collected at that point to be dumped to @file{.gcda} output files.
 Instrumented applications use a static destructor with priority 99
 to invoke the @code{__gcov_dump} function. Thus @code{__gcov_dump}
 is executed after all user defined static destructors,


                 reply	other threads:[~2021-05-28 11:38 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=20210528113828.73B743857804@sourceware.org \
    --to=marxin@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: 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).