On 3/14/23 15:21, Eugene Rozenfeld wrote:
From 1808fe371ab5618b7c0ce22c0dbecdaf593e516d Mon Sep 17 00:00:00 2001
From: Eugene Rozenfeld
Date: Mon, 21 Nov 2022 13:33:38 -0800
Subject: [PATCH] Fix autoprofiledbootstrap build
1. Fix gcov version
2. Merge perf data collected when compiling the c
To: Eugene Rozenfeld ; gcc-patches@gcc.gnu.org;
Andi Kleen
Subject: Re: [EXTERNAL] Re: [PATCH] Fix autoprofiledbootstrap build
[You don't often get email from jeffreya...@gmail.com. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
On 11/22/22 14:20, E
: Eugene Rozenfeld ; gcc-patches@gcc.gnu.org;
Andi Kleen
Subject: Re: [EXTERNAL] Re: [PATCH] Fix autoprofiledbootstrap build
[You don't often get email from jeffreya...@gmail.com. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
On 11/22/22 14:20, Eugene Roze
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 c
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
be
