mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: ingo@pyrillion.org
Cc: Andi Kleen <ak@muc.de>,
	j.dittmer@portrix.net, linux-kernel@vger.kernel.org
Subject: Re: Re: new icc kernel patch available (with kernel PGO)
Date: 8 Jun 2004 11:02:47 +0200	[thread overview]
Date: Tue, 8 Jun 2004 11:02:47 +0200	[thread overview]
Message-ID: <20040608090247.GB659@colin2.muc.de> (raw)
In-Reply-To: <5685161$108663562940c4be6d58edc6.52713007@config7.schlund.de>

On Mon, Jun 07, 2004 at 09:20:02PM +0200, ingo@pyrillion.org wrote:
> as I stated before, I created a generic training set in phase 2 of the
> three phases compilation process by utilizing the kernel in various
> ways: fore- and background activities, networking, filesystems, etc.

Ok.

> The PGO kernel module and the PGO daemon pgod are included in the
> newest patch. You can create your own specialized training set for your
> specific task. That's the big advantage of kernel PGO. This is the
> first patch using both technologies of the Intel C/C++ Compiler, IPO
> (Inter Procedural Optimization) and PGO (Profile Guided Optimization),
> together.

gcc supports PGO and even some forms of IPO just fine too, but it was never 
done because it causes maintainability issues (nobody can reproduce your binary
image anymore, which makes it extremly hard to reproduce an oops) 

BTW Someone pointed out that you're using flags to enable ansi aliasing
in your patchkit. That's an extremly bad idea, because the kernel
is not ANSI alias clean at all. If it worked you were quite lucky.

-Andi

  reply	other threads:[~2004-06-08  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 19:20 ingo
2004-06-08  9:02 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07 15:52 ingo

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=20040608090247.GB659@colin2.muc.de \
    --to=ak@muc.de \
    --cc=ingo@pyrillion.org \
    --cc=j.dittmer@portrix.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®