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/96919] [GCOV] uncovered line of stack allocation while using virutal destructor Date: Tue, 29 Sep 2020 07:48:05 +0000 [thread overview] Message-ID: <bug-96919-4-6rvtVRLCwq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96919-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96919 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org Target Milestone|--- |11.0 Status|NEW |ASSIGNED --- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> --- > > So according to your analysis would you classify this issue as a bug? Or is > it an NBC change that was introduced? Hard to say as C++ language introduces quite some boilerplate code that is not explicitly written by a code author. We identify these blocks in JSON format as exceptional, let me try to ignore these when outputting '#####'. > > /Filip
next prev parent reply other threads:[~2020-09-29 7:48 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-03 13:18 [Bug gcov-profile/96919] New: " youngseok.roh.de at gmail dot com 2020-09-21 11:00 ` [Bug gcov-profile/96919] " marxin at gcc dot gnu.org 2020-09-21 11:05 ` marxin at gcc dot gnu.org 2020-09-28 13:19 ` filip.pudak at gmail dot com 2020-09-29 7:48 ` marxin at gcc dot gnu.org [this message] 2020-10-02 11:29 ` marxin at gcc dot gnu.org 2020-10-26 7:13 ` libin.dang at gmail dot com 2020-10-26 14:55 ` marxin at gcc dot gnu.org 2020-11-17 15:06 ` bhavana.kilambi at blackfigtech dot com 2020-12-02 17:08 ` bhavana.kilambi at blackfigtech dot com 2020-12-02 17:10 ` bhavana.kilambi at blackfigtech dot com 2020-12-03 10:01 ` marxin at gcc dot gnu.org 2020-12-29 9:17 ` bhavana.kilambi at blackfigtech dot com 2021-01-06 11:55 ` marxin at gcc dot gnu.org 2021-01-06 13:55 ` bhavana.kilambi at blackfigtech dot com 2021-01-07 13:27 ` marxin at gcc dot gnu.org 2022-04-21 9:29 ` marxin at gcc dot gnu.org 2023-04-03 9:04 ` marxin 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-96919-4-6rvtVRLCwq@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).