From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2766E385741F; Tue, 25 May 2021 18:40:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2766E385741F From: "gejoed at rediffmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/100751] __gcov_dump and __gcov_reset usage Date: Tue, 25 May 2021 18:40:12 +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: gejoed at rediffmail dot com 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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2021 18:40:12 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100751 --- Comment #8 from Gejoe --- (In reply to Martin Li=C5=A1ka from comment #6) > 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. But reset comes into a picture where something has happened already and then the result needs to be cleared, isn't it ? At the application start, applyi= ng a reset would not make sense I think. gcov_reset would be sensible only after= a gcov_dump , isn't it ? Let me know if I miss the actual design/flow of these functions. Thanks !=