From: Diego Novillo <dnovillo@google.com>
To: Haifeng He <hehaifeng2nd@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: How to instrument a program using GCC
Date: Tue, 19 Feb 2008 13:38:00 -0000 [thread overview]
Message-ID: <47BACBA4.20401@google.com> (raw)
In-Reply-To: <ab08258e0802182012i56688cd9neaa1017a2ecab66a@mail.gmail.com>
On 2/18/08 11:12 PM, Haifeng He wrote:
> Thanks for replying. I searched online but could not find much information about
> GCC tree-profiling. GCC Internal also does not explain much on that. Is there
> any other document explains that subject? Or some kind of tutorial or small
> example that demonstrates how to manipulate GIMPLE tree will be also very
> helpful.
If you just want GCC to instrument your program, then reading on how to
use the -fprofile-* switches should be enough. Both are in the user
manual that comes with GCC.
If you want to know *how* these options work, that's different. A good
starting point is the GCC wiki. In particular,
http://gcc.gnu.org/wiki/GettingStarted
Diego.
next prev parent reply other threads:[~2008-02-19 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 23:07 Haifeng He
2008-02-17 20:17 ` Diego Novillo
2008-02-19 4:12 ` Haifeng He
2008-02-19 13:38 ` Diego Novillo [this message]
2008-02-19 21:10 ` Haifeng He
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=47BACBA4.20401@google.com \
--to=dnovillo@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=hehaifeng2nd@gmail.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).