git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Add explanation of the profile feedback build to the README

From
AKAndi Kleen <andi@firstfloor.org>
Date
Jun 20, 2011, 22:41 UTC
Message-ID
<1308609661-28650-1-git-send-email-andi@firstfloor.org>
From: Andi Kleen <ak@linux.intel.com>
Also explains that the are additional warnings.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 INSTALL |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/INSTALL b/INSTALL
index 16e45f1..bbb9d4d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -25,6 +25,19 @@ set up install paths (via config.mak.autogen), so you can write instead
 	$ make all doc ;# as yourself
 	# make install install-doc install-html;# as root
 
+If you're willing to trade off (much) longer build time for a later
+faster git you can also do a profile feedback build with
+
+	$ make profile-all
+	# make prefix=... install
+
+This will run the complete test suite as training workload and then
+rebuild git with the generated profile feedback. This results in a git
+which is a few percent faster on CPU intensive workloads.  This
+may be a good tradeoff for distribution packagers.
+
+Note that the profile feedback build stage currently generates
+a lot of additional compiler warnings.
 
 Issues of note:
 
-- 
1.7.4.4
Message 1 of 1 in “Add explanation of the profile feedback build to the README”
  1. Add explanation of the profile feedback build to the READMEAndi Kleen, Jun 20, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.