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, 18 Apr 2023 13:02:56 -0600 [thread overview]
Message-ID: <f4fe0f1f-f524-c515-99d5-3d48a3690b13@gmail.com> (raw)
In-Reply-To: <DS7PR21MB34793447F2B7257A661FC8FB91BE9@DS7PR21MB3479.namprd21.prod.outlook.com>
On 3/14/23 15:21, Eugene Rozenfeld wrote:
> From 1808fe371ab5618b7c0ce22c0dbecdaf593e516d Mon Sep 17 00:00:00 2001
> From: Eugene Rozenfeld<erozen@microsoft.com>
> 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 compiler and runtime libraries
> 3. Fix documentation typo
>
> Tested on x86_64-pc-linux-gnu.
>
> gcc/ChangeLog:
>
> * Makefile.in: Define PROFILE_MERGER
> * Makefile.tpl: Define PROFILE_MERGER
> * c/Make-lang.in: Merge perf data collected when compiling cc1 and runtime libraries
> * cp/Make-lang.in: Merge perf data collected when compiling cc1plus and runtime libraries
> * lto/Make-lang.in: Merge perf data collected when compiling lto1 and runtime libraries
> * doc/install.texi: Fix documentation typo
OK
jeff
prev parent reply other threads:[~2023-04-18 19:02 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
2023-03-14 21:21 ` Eugene Rozenfeld
2023-03-27 20:36 ` Eugene Rozenfeld
2023-04-18 19:02 ` Jeff Law [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=f4fe0f1f-f524-c515-99d5-3d48a3690b13@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).