public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mwd at md5i dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov Date: Tue, 29 Aug 2023 16:21:37 +0000 [thread overview] Message-ID: <bug-110827-4-0lyXQNRmHz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110827-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 Michael Duggan <mwd at md5i dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #55648|0 |1 is obsolete| | --- Comment #7 from Michael Duggan <mwd at md5i dot com> --- Created attachment 55812 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55812&action=edit Better example This example has both a coroutine and a non-coroutine with the same contents. Rather than using cout, it calls an empty function that is designed to not be optimized away.
next prev parent reply other threads:[~2023-08-29 16:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 2:34 [Bug gcov-profile/110827] New: " mwd at md5i dot com 2023-07-27 7:48 ` [Bug gcov-profile/110827] " rguenth at gcc dot gnu.org 2023-07-27 8:06 ` iains at gcc dot gnu.org 2023-07-27 13:56 ` mwd at md5i dot com 2023-07-27 17:34 ` mwd at md5i dot com 2023-07-28 6:17 ` rguenth at gcc dot gnu.org 2023-07-28 9:41 ` iains at gcc dot gnu.org 2023-08-29 16:21 ` mwd at md5i dot com [this message] 2023-08-29 16:40 ` mwd at md5i dot com 2023-08-31 16:53 ` mwd at md5i dot com 2023-09-25 18:05 ` mwd at md5i dot com 2023-09-26 14:54 ` iains 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-110827-4-0lyXQNRmHz@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).