public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/96913] [10 regression] gcov TOPN streaming is incorrect for shared libraries Date: Tue, 22 Sep 2020 10:44:27 +0000 [thread overview] Message-ID: <bug-96913-4-f1i4qkb92q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96913-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96913 Sergei Trofimovich <slyfox at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11 regression] gcov |[10 regression] gcov TOPN |TOPN streaming is incorrect |streaming is incorrect for |for shared libraries |shared libraries --- Comment #8 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- Should be fixed for gcc-11. Will send a backport to gcc-10 this evening (the code changed slightly since gcc-10).
next prev parent reply other threads:[~2020-09-22 10:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-03 7:39 [Bug gcov-profile/96913] New: gcc-11: __gcov_merge_topn hangs slyfox at gcc dot gnu.org 2020-09-03 7:41 ` [Bug gcov-profile/96913] " slyfox at gcc dot gnu.org 2020-09-04 15:26 ` slyfox at gcc dot gnu.org 2020-09-04 21:31 ` slyfox at gcc dot gnu.org 2020-09-06 10:23 ` slyfox at gcc dot gnu.org 2020-09-06 11:25 ` slyfox at gcc dot gnu.org 2020-09-06 11:31 ` [Bug gcov-profile/96913] [10/11 regression] gcov TOPN streaming is incorrect for shared libraries slyfox at gcc dot gnu.org 2020-09-22 10:42 ` cvs-commit at gcc dot gnu.org 2020-09-22 10:44 ` slyfox at gcc dot gnu.org [this message] 2020-10-02 10:04 ` [Bug gcov-profile/96913] [10 " slyfox at gcc dot gnu.org 2020-10-02 12:30 ` cvs-commit at gcc dot gnu.org 2020-10-02 12:32 ` slyfox at gcc dot gnu.org
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-96913-4-f1i4qkb92q@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: linkBe 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).