public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/48361] gcov freezes when using --all-blocks (-a) flag.
Date: Fri, 25 Sep 2020 08:51:20 +0000 [thread overview]
Message-ID: <bug-48361-4-pfHxVPCL5L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48361-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48361
--- Comment #19 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Prasannanjaneyulu from comment #18)
> Thank you @martin. I am not sure whether ubuntu 16.04 is compatible with gcc
> 8.4.0. Our app. is currently built for ubuntu 16.04 and I don't know what
> breaking changes it could bring if we upgrade gcc.
I strongly recommend to update to a supported GCC. Note that in the meantime
we've fixed many issues that can theoretically affect your application.
>
> Do you know any workaround other than disabling the whole branch coverage?
No.
prev parent reply other threads:[~2020-09-25 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 11:56 [Bug gcov-profile/48361] New: " lieutenantfeist at hotmail dot de
2011-05-20 17:46 ` [Bug gcov-profile/48361] " marc.glisse at normalesup dot org
2012-05-21 21:08 ` ben at salilab dot org
2012-07-22 0:20 ` steven at gcc dot gnu.org
2013-11-21 18:54 ` tim.besard at gmail dot com
2014-01-21 8:40 ` chan.pen.cheong at gmail dot com
2014-03-06 1:19 ` john.carter at taitradio dot com
2020-09-24 15:44 ` p.padavala at camlintechnologies dot com
2020-09-25 8:35 ` marxin at gcc dot gnu.org
2020-09-25 8:49 ` p.padavala at camlintechnologies dot com
2020-09-25 8:51 ` marxin at gcc dot gnu.org [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=bug-48361-4-pfHxVPCL5L@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).