From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from f4mail-235-222.rediffmail.com (f4mail-235-222.rediffmail.com [202.137.235.222]) by sourceware.org (Postfix) with ESMTPS id F2E7C3AA9836 for ; Mon, 3 Jun 2024 13:00:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F2E7C3AA9836 Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=rediffmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=rediffmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org F2E7C3AA9836 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=202.137.235.222 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1717419646; cv=none; b=IAB8jlAen+PjR8CvLHrQTnB75deJDWhPZjyVo4pmUf4Nhxha+8TgSHX6+tPp2KaSGioKhFg/T7vMKCDsDfOrZE7Nq0XS+8U6u7+tVvjjSc+gjo9cc/ub/CtzMRZL0TnZcAcPaDbrRmhKLq3ReSfHRlSfAV5NWkFgtj6GbLcdXzY= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1717419646; c=relaxed/simple; bh=rTBSrourTDE7Dc+0ECc4TJHfViiVyq0JeNFGf0RGKY4=; h=DKIM-Signature:Date:MIME-Version:To:Message-ID:Subject:From; b=hra7nzRbF2Bua0NJ4XB5xM8IyoyKgCPa28GZhzqUpYR9EjmVqOwfomL+qURQSm/dzwrqaAwWEegIWRo96BO9EuBjHhbPjw2suc9dDgmLpWZJu7PodxCnSYkdzrILeM/yQK08aedCMflL9rYjALjf/ZcVSVF9z1tcHUuzXp2pX8E= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rediffmail.com; s=mail; t=1717419638; bh=rTBSrourTDE7Dc+0ECc4TJHfViiVyq0JeNFGf0RGKY4=; h=MIME-Version:From:Date:Message-ID:Subject:To:Content-Type; b=hu1ReQptSJLNmcpUjZNMyjzFYYoD+4Xenry9JevseNVZI5DCsqz4AuFYMyEaMvWQG 48ZYz3euYRhbOMo0lImSN4akEHpzzNIEwxTAjC4UN3K6LHWD16XkNBI3I6vqomsHzI hupXlAa/yYUnKWXjxVzGzRGV4rHQo7EM1PROz1Tg= Received: (qmail 8325 invoked by uid 510); 3 Jun 2024 13:00:38 -0000 x-m-msg: asd54ad564ad7aa6sd5as6d5; a6da7d6asas6dasd77; 5dad65ad5sd; X-OUT-VDRT-SpamState: 0\LEGIT X-OUT-VDRT-SpamScore: 40 X-OUT-VDRT-SpamCause: gggruggvucftvghtrhhoucdtuddrgedvledrvdelvddgheelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecutffgfffkhffhpdfqfgfvnecuuegrihhlohhuthemuceftddtnecuhfhorhhgvgguucfjvffvrffuucdlgedtmdenucfjughrpeffggfvkfgjshfuhfgtsegrtderredttdejnecuhfhrohhmpedfifgvjhhovgcuffgrnhhivghlfdcuoehgvghjohgvugesrhgvughifhhfmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpefhudeijeehtdeutdduheejieevffekgefgjeekieeiteegkedthefhledtieejleenucffohhmrghinhepghhnuhdrohhrghdprhgvughifhhfrdgtohhmnecukfhppeejvddrudeifedrvddvtddrvdelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpohhuth X-Remote-IP: 72.163.220.29 X-REDF-OSEN: gejoed@rediffmail.com Date: 3 Jun 2024 13:00:37 -0000 MIME-Version: 1.0 To: "gcc-help@gcc.gnu.org" Received: from unknown 72.163.220.29 by rediffmail.com via HTTP; 03 Jun 2024 13:00:37 -0000 X-Senderscore: D=0&S=0 Message-ID: <1716354425.S.6834.26430.f4mail-235-104.rediffmail.com.1717419637.8254@webmail.rediffmail.com> In-Reply-To: <1716354123.S.18546.autosave.drafts.1716354425.26333@webmail.rediffmail.com> Sender: gejoed@rediffmail.com Subject: =?utf-8?B?UmU6IFtSZWdhcmRpbmcgIEdDT1ZdLmdjZGE6c3RhbXAgbWlzbWF0Y2ggd2l0aCBub3RlcyBmaWxl?= From: "Gejoe Daniel" Content-Type: multipart/alternative; boundary="=_3d92fbd7daef4b1caf58dc8b264ec3fc" X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,KAM_SHORT,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --=_3d92fbd7daef4b1caf58dc8b264ec3fc Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Ignore this email as I have posted the message in bugzilla page. Sorry for this email to your inbox. Thanks, Gejoe  From: "Gejoe Daniel"<gejoed@rediffmail.com> Sent: Wed, 22 May 2024 10:37:05 To: "gcc-help@gcc.gnu.org"<gcc-help@gcc.gnu.org> Subject: [Regarding GCOV].gcda:stamp mismatch with notes file Hi GCC Gcov experts, I would like to know if the stamp value (present in gcno files) generated during build can get modified during a compilation /recompilation (when multiple components are involved through Makefiles) or can the gcda stamp value get modified during the gcda collection ( __gcov_dump() API invocation ) ? Since with gcc 11.4.0 we see gcda stamps mismatch with gcno stamps , I'm trying to figure out when any of these values can get modified (considering a gcov enabled build and then the testing of the image built). In my project case, not all gcda stamps mismatch with respective gcno stamps. Some of them show coverage % without any stamp mismatch issue. For eg, for a problematic stamp case (quoting the stamp value from the output of gcov_dump tool for the respective source file.gcda and gcno files): C-src-filename.gcda:stamp 2912455990  C-src-filename.gcno:stamp 2912494680     If we see here, the gcno stamp value seems higher and how do we try to debug the case here ? Is gcno stamp getting modified during the build or is gcda stamp getting modified (after testing and during collection of gcda files from device) ?  The context of this query can be understood from email below and a previous bugzilla link. Awaiting some inputs from gcov experts. Thanks, Gejoe  From: "Gejoe Daniel"<gejoed@rediffmail.com> Sent: Mon, 29 Apr 2024 17:16:23 To: "gcc-help@gcc.gnu.org"<gcc-help@gcc.gnu.org> Subject: Re: [Regarding GCOV].gcda:stamp mismatch with notes file Hi all, Reaching out to the helpers list to know if someone can give any inputs. Thanks, Gejoe From: "Gejoe Daniel"<gejoed@rediffmail.com> Sent: Thu, 25 Apr 2024 12:15:58 To: <gcc@gcc.gnu.org>,<gcc-help@gcc.gnu.org> Subject: [Regarding GCOV].gcda:stamp mismatch with notes file Hi team, The following is my query posted but would need more inputs : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114751 The gcov tool which was working so far seems to fail with our latest branch where gcc is 11.4.0 and hence we wanted to sort this out by getting the right help as early as possible. Awaiting prompt reply. Thanks to the GCC team for all the help ! Regards, Gejoe --=_3d92fbd7daef4b1caf58dc8b264ec3fc--