From: SAIFI <saifi@strikr.io>
To: gcc@gcc.gnu.org
Subject: Re: GCC Plugin introduction
Date: Tue, 30 Mar 2021 10:53:50 +0100 (BST) [thread overview]
Message-ID: <ef12e0f-a991-ca3f-2f30-bb586b709b85@strikr.io> (raw)
In-Reply-To: <4b099fce-df0c-34dd-644e-fec2042e568e@santannapisa.it>
On Mon, 29 Mar 2021, Gabriele Serra wrote:
>
> I have written a very basic article on GCC Plugins (how to build a plugin
> from the ground, some info on APIs, and how to instrument code). The material
> is based on GCC 9. The code is fully documented and working.
>
> https://gabrieleserra.ml/blog/2020-08-27-an-introduction-to-gcc-and-gccs-plugins.html
>
Gabriele thanks for sharing the detailed write up.
in the spirit of 'gcc-help', can you please share pointers as to how one can profile C++ code using GCC plugins ?
in your example you mention 'f1 ()'; i'd like to replace that with a instance of class 'X' created and then profile or instrument a member function.
Have you explored that ? any preliminary thoughts on how does one go about doing it ?
warm regards
Saifi.
next prev parent reply other threads:[~2021-03-30 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 9:25 Gabriele Serra
2021-03-30 9:53 ` SAIFI [this message]
2021-04-01 10:25 ` SAIFI
2021-03-30 14:11 Gabriele Serra
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=ef12e0f-a991-ca3f-2f30-bb586b709b85@strikr.io \
--to=saifi@strikr.io \
--cc=gcc@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).