From: "Martin Liška" <mliska@suse.cz>
To: Alexander Fichtinger <alexander.fichtinger@logicals.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: AW: AW: Problem using gcov
Date: Mon, 26 Feb 2018 14:35:00 -0000 [thread overview]
Message-ID: <82d31942-b9ee-8b51-6bef-f6f6481ff703@suse.cz> (raw)
In-Reply-To: <kcim.5a94138c.2926.7f0d9fa9758034a3@v-srvkopano.ow.ks>
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.
I did, but as described in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84572#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
>
> When is 8.0 going to be released?
>
> Thanks and kind regards,
> Alexander
>
> -----UrsprĂźngliche Nachricht-----
> Von: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] Im Auftrag von Martin Liška
> Gesendet: Montag, 26. Februar 2018 14:57
> An: Alexander Fichtinger <alexander.fichtinger@logicals.com>; 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 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 which I called.
>>
>> And the line with the "strange" execution count is also mentioned.
>>
>> Thank you and kind regards,
>>
>> Alexander
>>
>>
>> -----UrsprĂźngliche Nachricht-----
>> Von: Martin Liška [mailto:mliska@suse.cz]
>> Gesendet: Donnerstag, 22. Februar 2018 10:43
>> An: Alexander Fichtinger <alexander.fichtinger@logicals.com>; 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 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=84572
>
> Martin
>
next prev parent reply other threads:[~2018-02-26 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 13:33 Alexander Fichtinger
2018-02-22 9:43 ` Martin Liška
[not found] ` <kcim.5a93e1c0.2b51.26a60a650176b62e@v-srvkopano.ow.ks>
2018-02-26 13:57 ` AW: " Martin Liška
2018-02-26 14:03 ` AW: " Alexander Fichtinger
2018-02-26 14:27 ` Jonathan Wakely
2018-02-26 14:35 ` Martin Liška [this message]
2018-02-26 14:41 ` AW: AW: " Alexander Fichtinger
2018-02-27 8:13 ` Martin Liška
2018-02-27 10:01 ` AW: " Alexander Fichtinger
2018-02-27 12:43 ` Martin Liška
2018-02-27 12:53 ` AW: " Alexander Fichtinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82d31942-b9ee-8b51-6bef-f6f6481ff703@suse.cz \
--to=mliska@suse.cz \
--cc=alexander.fichtinger@logicals.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).