From: Roger Phillips <heidegg@hotmail.com>
To: "Martin Liška" <mliska@suse.cz>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: "weixi.wwx@antfin.com" <weixi.wwx@antfin.com>
Subject: Re: SanitizerCoverage support
Date: Wed, 20 Jan 2021 22:50:19 +0000 [thread overview]
Message-ID: <DM5PR06MB2555663E0C4199C57978B34DAAA20@DM5PR06MB2555.namprd06.prod.outlook.com> (raw)
In-Reply-To: <7a99a7ae-35b6-fb01-e270-1d9e7af1cf08@suse.cz>
Would it be possible to replicate the sancov functionality on gcc just through special trace functions?
________________________________
From: Martin Liška <mliska@suse.cz>
Sent: Wednesday, January 20, 2021 11:40 AM
To: Roger Phillips <heidegg@hotmail.com>; gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Cc: weixi.wwx@antfin.com <weixi.wwx@antfin.com>
Subject: Re: SanitizerCoverage support
On 1/19/21 12:11 PM, Roger Phillips wrote:
> Does any of these two modes allow me to generate sancov files on function level? My intent is to record program flow, then visualize the diff between the runs. Most examples I see use edge,bb,func modes so I'm not sure trace-pc and trace-pc-cmp are enough.
I think we likely miss the functionality. I briefly looked at:
https://clang.llvm.org/docs/SanitizerCoverage.html and
as shown here:
https://clang.llvm.org/docs/SanitizerCoverage.html#default-implementation
On the other hand, the functionality should be in sanitizer so we may use it.
Martin
next prev parent reply other threads:[~2021-01-20 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 9:07 Roger Phillips
2021-01-19 10:23 ` Martin Liška
2021-01-19 10:33 ` Roger Phillips
2021-01-19 10:40 ` Martin Liška
2021-01-19 11:11 ` Roger Phillips
2021-01-20 11:40 ` Martin Liška
2021-01-20 22:50 ` Roger Phillips [this message]
2021-01-22 13:23 ` Martin Liška
2021-01-19 14:51 ` Roger Phillips
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=DM5PR06MB2555663E0C4199C57978B34DAAA20@DM5PR06MB2555.namprd06.prod.outlook.com \
--to=heidegg@hotmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=weixi.wwx@antfin.com \
/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).