qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [patch] make qemu work with GCC 4
Date: Thu, 30 Aug 2007 18:52:19 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708301849180.23011@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291842500.23011@wotan.suse.de>

Hi,

On Wed, 29 Aug 2007, Michael Matz wrote:

> > >        I solved that by placing one of the T[012] operands into memory
> > >        for HOST_I386, thereby freeing one reg.  Here's some justification
> > >        of why that doesn't really cost performance: with three free regs
> > >        GCC is already spilling like mad in the snippets, we just trade one
> > >        of those memory accesses (to stack) with one other mem access to
> > >        the cpu_state structure, which will be in cache.
> > 
> > Do you have any evidence to support this claim?
> 
> Not really, only an apple and orange comparison.  A 10000 iteration 
> tests/sha1 run in the same Linux image, with -no-kqemu, on host and target 
> i386:  time ./sha1
> 
> with qemu-0.8.2 (compiled by gcc 3.3-hammer): 7.92 seconds
> with qemu-0.9.0-cvs (gcc4.1 compiled, with the patch): 8.15 seconds
> 
> I'll try to get a better comparison.

So, I've now compared our 0.9.0 package, once without patch compiled by 
3.3-hammer, and once with patch and compiled by gcc 4.2:

gcc33 compiled: 7.81 seconds (i.e. a bit faster than 0.8.2 was)
gcc42 compiled: 8.07 seconds

I.e. 3% slower.


Ciao,
Michael.

  reply	other threads:[~2007-08-30 16:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 19:57 [Qemu-devel] [patch] make qemu work with GCC 4 Michael Matz
2007-08-29  8:41 ` Andreas Färber
2007-08-29 11:40   ` Michael Matz
2007-08-29 13:14     ` Andreas Färber
2007-08-29 13:30       ` Michael Matz
2007-08-29 13:59         ` Mulyadi Santosa
2007-08-29 14:11           ` Johannes Schindelin
2007-08-29 16:40             ` Michael Matz
2007-08-29 16:55               ` Johannes Schindelin
2007-08-29 18:09                 ` Blue Swirl
2007-08-30 12:46         ` Carlo Marcelo Arenas Belon
2007-08-29 13:59       ` Johannes Schindelin
2007-08-29 14:13         ` Ronald
2007-08-29 14:19           ` Johannes Schindelin
2007-08-29 14:38             ` Andreas Färber
2007-08-29 14:27         ` Andreas Färber
2007-08-29 11:08 ` Johannes Schindelin
2007-08-29 11:46   ` Michael Matz
2007-08-29 12:40     ` Johannes Schindelin
2007-08-29 15:06 ` Paul Brook
2007-08-29 17:29   ` Michael Matz
2007-08-30 16:52     ` Michael Matz [this message]
2007-08-29 18:08 ` Anthony Liguori
2007-08-30 20:28 ` Thiemo Seufer
2007-08-31 13:31   ` Michael Matz
2007-08-31 14:17     ` Thiemo Seufer

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=Pine.LNX.4.64.0708301849180.23011@wotan.suse.de \
    --to=matz@suse.de \
    --cc=agraf@suse.de \
    --cc=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).