qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] yet another proposed solution for gcc 4.x
Date: Mon, 5 Jun 2006 14:49:03 +0100	[thread overview]
Message-ID: <200606051449.04585.paul@codesourcery.com> (raw)
In-Reply-To: <20060605134346.GE26124@tapir.sajinet.com.pe>

(everything compiled with gcc3)
> user    0m0.250s
> 9.44444
(everything compiled with gcc4)
> user    0m0.284s
> 9.25806

Your comparison is not valid. You should only change one variable at once.
We don't care whether a gcc4 sha1 is faster or slower than gcc3 sha1. By your 
own numbers gcc4 is slower in absolute terms. We only care whether qemu goes 
faster or slower when running the same binary.

You should also state how any runs you did and what the variation is. 
Especially on modern systems there can be a lot of variation between 
successive runs.

> PS. is there any "standard" way to benchmark qemu that is all agreed upon as
> authoritative other than `make speed`?

Not really. Also, simple benchmarks (which tend to be dominated by a 
single "hot" loop) are not neccly a representative measure of qemu 
performance.

Paul

      reply	other threads:[~2006-06-05 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04  8:59 [Qemu-devel] yet another proposed solution for gcc 4.x Carlo Marcelo Arenas Belon
2006-06-04 11:46 ` Paul Brook
2006-06-04 16:02   ` Carlo Marcelo Arenas Belon
2006-06-05 11:21     ` Christian MICHON
2006-06-05 13:43       ` Carlo Marcelo Arenas Belon
2006-06-05 13:49         ` Paul Brook [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=200606051449.04585.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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).