public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vit9696 at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/105063] [GCOV] Ability to map .gcda paths Date: Thu, 31 Mar 2022 11:30:33 +0000 [thread overview] Message-ID: <bug-105063-4-YXBeGePStc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105063-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105063 --- Comment #10 from vit9696 <vit9696 at protonmail dot com> --- I believe this is possible. Since we use both clang and gcc, I filed an issue in llvm first to make sure both compilers can be updated in a similar way (https://github.com/llvm/llvm-project/issues/54670).
next prev parent reply other threads:[~2022-03-31 11:30 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-26 16:31 [Bug gcov-profile/105063] New: " vit9696 at protonmail dot com 2022-03-28 10:34 ` [Bug gcov-profile/105063] " marxin at gcc dot gnu.org 2022-03-30 9:15 ` vit9696 at protonmail dot com 2022-03-30 10:46 ` marxin at gcc dot gnu.org 2022-03-30 17:22 ` vit9696 at protonmail dot com 2022-03-31 7:06 ` marxin at gcc dot gnu.org 2022-03-31 7:19 ` vit9696 at protonmail dot com 2022-03-31 7:45 ` marxin at gcc dot gnu.org 2022-03-31 8:27 ` vit9696 at protonmail dot com 2022-03-31 8:46 ` marxin at gcc dot gnu.org 2022-03-31 11:30 ` vit9696 at protonmail dot com [this message] 2022-03-31 11:34 ` marxin at gcc dot gnu.org 2022-03-31 11:47 ` vit9696 at protonmail dot com 2022-03-31 12:27 ` marxin at gcc dot gnu.org 2022-03-31 16:16 ` vit9696 at protonmail dot com 2022-04-06 12:14 ` marxin at gcc dot gnu.org 2023-04-03 8:57 ` marxin at gcc dot gnu.org 2023-04-03 9:03 ` marxin at gcc dot gnu.org 2024-05-07 7:39 ` rguenth 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-105063-4-YXBeGePStc@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).