From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69495 invoked by alias); 27 Feb 2018 08:13:12 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 69486 invoked by uid 89); 27 Feb 2018 08:13:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-7.6 required=5.0 tests=BAYES_00,GIT_PATCH_2,KAM_SHORT,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=automotive, Automotive, HX-Priority:Normal, customers X-HELO: isc-mx.mymailwall.com Received: from isc-mx.mymailwall.com (HELO isc-mx.mymailwall.com) (91.212.136.3) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 27 Feb 2018 08:13:08 +0000 X-MyMailWallStatus: Email scanned(1117275058) Received: from mail.logicals.com (EHLO mail.logicals.com) [195.202.147.34] by mx.mymailwall.com with ESMTP TLS id 19561; Tue, 27 Feb 2018 09:13:02 +0100 Received: from v-srvkopano.ow.ks (localhost [127.0.0.1]) by v-srvkopano.ow.ks (Postfix) with ESMTP id 5160837DE37; Tue, 27 Feb 2018 09:13:02 +0100 (CET) Received: by v-srvkopano (kopano-spooler) with MAPI; Tue, 27 Feb 2018 09:13:02 +0100 Subject: =?iso-8859-2?Q?AW=3A_AW=3A_AW=3A_AW=3A_Problem_using_gcov?= From: =?iso-8859-2?Q?Alexander_Fichtinger?= To: =?iso-8859-2?Q?Martin_Li=B9ka?= , =?iso-8859-2?Q?gcc=40gcc=2Egnu=2Eorg?= Date: Tue, 27 Feb 2018 10:01:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <0c98dc62-0de0-77b5-3681-cbc68a6dfa78@suse.cz> <83da2297-f60d-a9ef-91aa-5ec62497a47c@suse.cz> <82d31942-b9ee-8b51-6bef-f6f6481ff703@suse.cz> Message-Id: X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00219.txt.bz2 Ok, thanks for the information. Do we get all coverage-related problems when we monitor the Bugs with the C= omponent "gcov-profile"? Or are there other components concerning coverage? We are using gcov in our Testframework (used for Automotive software) in or= der to determine the Code-Coverage,=20 so it is important for us to know if there are any bugs which could comprom= ise the reported test coverage. Thanks and kind regards, Alexander -----Urspr=FCngliche Nachricht----- Von: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] Im Auftrag von Ma= rtin Li=B9ka Gesendet: Dienstag, 27. Februar 2018 09:01 An: Alexander Fichtinger ; gcc@gcc.gnu.o= rg Betreff: Re: AW: AW: AW: Problem using gcov On 02/26/2018 03:41 PM, Alexander Fichtinger wrote: > Ok, thanks for the info. >=20 > I just saw the description in the bug-report. > When we document this for our customers, it's ok, I think.=20 Thanks for understanding. I would just note that there's couple of similar = issues you probably want to be aware of: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83434 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83505 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83587 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83616 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83678 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83813 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D83813 Martin >=20 > Thanks and kind regards, > Alexander >=20 > -----Urspr=FCngliche Nachricht----- > Von: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] Im Auftrag=20 > von Martin Li=B9ka > Gesendet: Montag, 26. Februar 2018 15:36 > An: Alexander Fichtinger ;=20 > gcc@gcc.gnu.org > Betreff: Re: AW: AW: Problem using gcov >=20 > On 02/26/2018 03:02 PM, Alexander Fichtinger wrote: >> Thanks Martin! >> >> I've seen that the target milestone for this bug is 8.0. >=20 > I did, but as described in=20 > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D84572#c1 > I'm not planning to fix it in the next releases. It's just a minor issue = in GCOV infrastructure. >=20 > Thank you for understanding, > Martin >=20 >> >> When is 8.0 going to be released? >> >> Thanks and kind regards, >> Alexander >> >> -----Urspr=FCngliche Nachricht----- >> Von: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] Im Auftrag=20 >> von Martin Li=B9ka >> Gesendet: Montag, 26. Februar 2018 14:57 >> An: Alexander Fichtinger ; >> gcc@gcc.gnu.org >> Betreff: Re: AW: Problem using gcov >> >> On 02/26/2018 11:30 AM, Alexander Fichtinger wrote: >>> Hi Martin, >>> >>> sorry that it took me so long to create the standalone sample, but I wa= s very busy the last few days. >>> >>> >>> We can reproduce the strange behavior in a standalone scenario. >>> >>> I've provided it in the attachments. >>> In the ZIP-file there is also a README.txt which contains the commands = which I called. >>> >>> And the line with the "strange" execution count is also mentioned. >>> >>> Thank you and kind regards, >>> >>> Alexander >>> >>> >>> -----Urspr=FCngliche Nachricht----- >>> Von: Martin Li=B9ka [mailto:mliska@suse.cz] >>> Gesendet: Donnerstag, 22. Februar 2018 10:43 >>> An: Alexander Fichtinger ; >>> gcc@gcc.gnu.org >>> Betreff: Re: Problem using gcov >>> >>> On 02/21/2018 02:33 PM, Alexander Fichtinger wrote: >>>> When you look at line 23 it is called 1 time. Line 24 is called 2 time= s (the bold one). >>>> We already looked in the disassembly but did not see a reason why the = line should be executed 2 times. >>>> >>>> Can anyone help here, please? >>>> >>>> Kind regards, >>>> Alex >>> >>> Hi. >>> >>> Sure, can you please send a self-contained test-case that I can run? >>> >>> Thank you, >>> Martin >>> >> >> No problem, I can confirm the problem: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D84572 >> >> Martin >> >=20 >=20