From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 7DE5638515D5; Wed, 26 May 2021 07:31:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7DE5638515D5
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/100751] __gcov_dump and __gcov_reset usage
Date: Wed, 26 May 2021 07:31:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-100751-4-a5fOzKXqcg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-100751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-100751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 07:31:14 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100751

--- Comment #9 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
(In reply to Gejoe from comment #8)
> (In reply to Martin Li=C5=A1ka from comment #6)
>=20
> > Yes, __gcov_reset is supposed to be called at the beginning when an
> > application wants to start
> > profiling. Again, you don't need to call it manually.
>=20
> But reset comes into a picture where something has happened already and t=
hen
> the result needs to be cleared, isn't it ?

It's the other way around, you start an application and then you decide you
want to start profiling, so you call __gcov_reste.

> At the application start,
> applying a reset would not make sense I think.

Yes, it does not make sense.

> gcov_reset would be sensible
> only after a gcov_dump , isn't it ?

No, as explained.

>=20
> Let me know if I miss the actual design/flow of these functions.

Btw. why do you need calling __gcov_dump and __gcov_reset manually? How is =
your
training run special?=