qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@cs.man.ac.uk>
To: Christian MICHON <christian.michon@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Profiling Qemu for speed?
Date: Mon, 18 Apr 2005 15:29:02 +0100	[thread overview]
Message-ID: <4263C42E.5030108@cs.man.ac.uk> (raw)
In-Reply-To: <46d6db66050418071228139ffd@mail.gmail.com>

Christian MICHON wrote:

>I did months ago gcc/FDO with a xp/lite installation as a "repetitive task" :)
>I did not improve the timings after all the effort.
>  
>
could this be down to the tables used to find the 
translators/generators? are they constant? is it possible to make them 
amenable to feedback directed analysis? x86 is also an odd case, it 
could be that load-store architectures with more registers notice FDO 
more as the x86 can access the L1 caches similarly to a large register 
file. If the problem is gcc's feedback analysis then you could always 
try Intel's compiler. Regards,

Ian Rogers
-- http://www.binarytranslator.org/

  reply	other threads:[~2005-04-18 14:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18  8:35 [Qemu-devel] Profiling Qemu for speed? Daniel J Guinan
2005-04-18  9:51 ` Ian Rogers
2005-04-18 13:44   ` Daniel Egger
2005-04-18 14:12     ` Christian MICHON
2005-04-18 14:29       ` Ian Rogers [this message]
2005-04-18 14:19     ` Ian Rogers
2005-04-18 14:40     ` Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2005-04-18 11:24 Daniel J Guinan
2005-04-17  5:58 Joe Luser
2005-04-17  8:21 ` John R. Hogerhuis
2005-04-17  8:59   ` Jonas Maebe
2005-04-17 10:27     ` Paul Brook
2005-04-17 10:46       ` Jonas Maebe
2005-04-18  1:36         ` Nathaniel G H
2005-04-18  2:11           ` John R. Hogerhuis
2005-04-18  2:39           ` André Braga
2005-04-18  4:31             ` Karl Magdsick
2005-04-17 10:36 ` Paul Brook

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=4263C42E.5030108@cs.man.ac.uk \
    --to=irogers@cs.man.ac.uk \
    --cc=christian.michon@gmail.com \
    --cc=ian.rogers@manchester.ac.uk \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).