From: Reetesh Ranjan <reeteshranjan@piaxis.tech>
To: Nathan Sidwell <nathan@acm.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: About hang in gcov_exit with gnu arm toolchain
Date: Sat, 03 Jun 2017 09:01:00 -0000 [thread overview]
Message-ID: <D9243BC0-99BF-4110-B7B2-73669A0FC7D4@piaxis.tech> (raw)
In-Reply-To: <25e39543-b4c7-c63d-80c7-69896b9100a4@acm.org>
Hi Nathan,
Please see comments inline.
> On 02-Jun-2017, at 5:14 PM, Nathan Sidwell <nathan@acm.org> wrote:
>
> hi,
>
>> I have opened this bug https://bugs.launchpad.net/gcc-arm-embedded/+bug/1694644 as per the findings I had.
>
> This is Canonical's bug tracker and you seem to be reporting a defect with their build of gcc. If that is the case, you should be talking with Canonical.
As you can see in the bug, they have redirected me to talk to gcc. Please advise on how to proceed.
>
> The gcc bug tracker is https://gcc.gnu.org/bugzilla/.
>
>
> The diff you provide there seems to be detecting when you've looped 2^32 times, because somethings scrogging the object list to become circular. That's the actual defect that needs fixing.
I studied the gcc/ and libgcc/ code. I cannot make out why this is happening, though the debugging session does show this clearly. What I am trying to do with the patch is to show what was required to make things work; however, as you said it is not the fix for the core issue.
About 2^32 times: yes if we had 2^32 files in any given project, it would definitely iterate that many times and fail. In what I saw with my debugging, the circular list contains as many elements as the number of source files in a project, and the loop iterates that many times. There could be a better way to iterate through a circular list, though.
>
> nathan
>
> --
> Nathan Sidwell
prev parent reply other threads:[~2017-06-03 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 8:15 Reetesh Ranjan
2017-06-02 11:44 ` Nathan Sidwell
2017-06-03 9:01 ` Reetesh Ranjan [this message]
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=D9243BC0-99BF-4110-B7B2-73669A0FC7D4@piaxis.tech \
--to=reeteshranjan@piaxis.tech \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.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).