From: Jeff Law <jeffreyalaw@gmail.com>
To: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [EXTERNAL] Re: [PATCH] Fix autoprofiledbootstrap build
Date: Tue, 22 Nov 2022 23:15:44 -0700 [thread overview]
Message-ID: <9c75978b-b7db-2a3e-f6f4-a2ff357387eb@gmail.com> (raw)
In-Reply-To: <CY5PR21MB3542545177751FFEA42448A7910D9@CY5PR21MB3542.namprd21.prod.outlook.com>
On 11/22/22 14:20, Eugene Rozenfeld wrote:
> I took another look at this. We actually collect perf data when building the libraries. So, we have ./prev-gcc/perf.data, ./prev-libcpp/perf.data, ./prev-libiberty/perf.data, etc. But when creating gcov data for -fauto-profile build of cc1plus or cc1 we only use ./prev-gcc/perf.data . So, a better solution would be either having a single perf.data for all builds (gcc and libraries) or merging perf.data files before attempting autostagefeedback. What would you recommend?
ISTM that if neither approach loses data, then they're functionally
equivalent -- meaning that we can select whichever is easier to wire
into our build system.
A single perf.data might serialize the build. So perhaps separate, then
merge right before autostagefeedback.
But I'm willing to go with whatever you think is best.
Jeff
next prev parent reply other threads:[~2022-11-23 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 21:57 Eugene Rozenfeld
2022-11-22 20:01 ` Jeff Law
2022-11-22 21:20 ` [EXTERNAL] " Eugene Rozenfeld
2022-11-23 6:15 ` Jeff Law [this message]
2023-03-14 21:21 ` Eugene Rozenfeld
2023-03-27 20:36 ` Eugene Rozenfeld
2023-04-18 19:02 ` Jeff Law
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=9c75978b-b7db-2a3e-f6f4-a2ff357387eb@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Eugene.Rozenfeld@microsoft.com \
--cc=ak@linux.intel.com \
--cc=gcc-patches@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).