From: Richard Biener <richard.guenther@gmail.com>
To: gcc@gcc.gnu.org,Qing Zhao <qing.zhao@oracle.com>
Subject: Re: Gcc profile questions
Date: Tue, 19 Feb 2019 17:07:00 -0000 [thread overview]
Message-ID: <A6CC83BF-8A6A-4D36-8315-03D0C6C8BAC1@gmail.com> (raw)
In-Reply-To: <03639D7B-C8CB-41A9-88DC-57B04D285677@oracle.com>
On February 19, 2019 5:19:11 PM GMT+01:00, Qing Zhao <qing.zhao@oracle.com> wrote:
>Hi,
>
>Suppose we have a program called foo which is built with gcc
>-fprofile-generate, Now when foo is executed a bunch of .gcda files
>are created.
>
>What happens when foo is executed more than once. Are the .gcda files
>updated with each execution?
Yes.
Or are the .gcda files overwritten with
>new .gcda files (and thus contain profile info only for the last
>execution)?
>
>Thanks for the info.
>
>Qing
prev parent reply other threads:[~2019-02-19 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 16:19 Qing Zhao
2019-02-19 17:07 ` Richard Biener [this message]
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=A6CC83BF-8A6A-4D36-8315-03D0C6C8BAC1@gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=qing.zhao@oracle.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).