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/107537] gcov skips throw/fallthrough annotations for 'never executed' branches
Date: Wed, 14 Dec 2022 13:45:13 +0000 [thread overview]
Message-ID: <bug-107537-4-2pm8CPzmK0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107537-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107537
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Hello. Sorry for the delay.
> Is there any reason why gcov skips throw/fallthrough annotations for
> branches which were never executed?
No. Your patch is fine and pre-approved, please include the PR entry in
ChangeLog and send it to gcc-patches. Once doing that, you can commit it (if
you have a copyright assignment and git write access?).
next prev parent reply other threads:[~2022-12-14 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 19:20 [Bug gcov-profile/107537] New: " grregd at gmail dot com
2022-11-10 14:19 ` [Bug gcov-profile/107537] " marxin at gcc dot gnu.org
2022-12-04 20:45 ` michael.foerderer at gmx dot de
2022-12-14 13:45 ` marxin at gcc dot gnu.org [this message]
2022-12-14 20:06 ` michael.foerderer at gmx dot de
2022-12-15 10:59 ` cvs-commit at gcc dot gnu.org
2022-12-15 11:00 ` 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-107537-4-2pm8CPzmK0@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).