From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8623 invoked by alias); 26 Feb 2018 14:41:23 -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 8607 invoked by uid 89); 26 Feb 2018 14:41:22 -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=HX-Priority:Normal, customers, our 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; Mon, 26 Feb 2018 14:41:21 +0000 X-MyMailWallStatus: Email scanned(1116869609) Received: from mail.logicals.com (EHLO mail.logicals.com) [195.202.147.34] by mx.mymailwall.com with ESMTP TLS id 19561; Mon, 26 Feb 2018 15:41:14 +0100 Received: from v-srvkopano.ow.ks (localhost [127.0.0.1]) by v-srvkopano.ow.ks (Postfix) with ESMTP id 5D8FA37DF88; Mon, 26 Feb 2018 15:41:15 +0100 (CET) Received: by v-srvkopano (kopano-spooler) with MAPI; Mon, 26 Feb 2018 15:41:15 +0100 Subject: =?iso-8859-2?Q?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: Mon, 26 Feb 2018 14:41:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable In-Reply-To: <82d31942-b9ee-8b51-6bef-f6f6481ff703@suse.cz> 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/msg00195.txt.bz2 Ok, thanks for the info. I just saw the description in the bug-report. When we document this for our customers, it's ok, I think.=20 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: Montag, 26. Februar 2018 15:36 An: Alexander Fichtinger ; gcc@gcc.gnu.o= rg Betreff: Re: AW: AW: Problem using gcov On 02/26/2018 03:02 PM, Alexander Fichtinger wrote: > Thanks Martin! >=20 > I've seen that the target milestone for this bug is 8.0. I did, but as described in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D8= 4572#c1 I'm not planning to fix it in the next releases. It's just a minor issue in= GCOV infrastructure. Thank you for understanding, Martin >=20 > When is 8.0 going to be released? >=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 14:57 > An: Alexander Fichtinger ;=20 > gcc@gcc.gnu.org > Betreff: Re: AW: Problem using gcov >=20 > 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 was= 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 w= hich 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 ;=20 >> 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 times= (the bold one). >>> We already looked in the disassembly but did not see a reason why the l= ine 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 >> >=20 > No problem, I can confirm the problem: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D84572 >=20 > Martin >=20