qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Falk Hueffner <hueffner@informatik.uni-tuebingen.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Performances on Mac OS X
Date: Mon, 02 Aug 2004 14:20:14 +0200	[thread overview]
Message-ID: <87brhtohoh.fsf@informatik.uni-tuebingen.de> (raw)
In-Reply-To: <1091448454.410e2e8606e5e@imp4-q.free.fr> (Laurent Amon's message of "Mon,  2 Aug 2004 14:07:34 +0200")

Laurent Amon <amon@stanfordalumni.org> writes:

> Just to let you know that I have been benchmarking with linux-test/nbench on my
> Titanium G4/400 and that I have been able to sqeeze a few percents (some 5%) of
> performance by compiling with -mcpu=7400 wirth GCC 3.3. This is the only flag
> that seems useful.
> I have also tried -mpowerpc-gpopt, -mpowerpc-gfxopt, -falign-loops,
> -funroll-loops, -fnew-ra, -ftracer.

Well, the instruction stubs don't contain loops and are short enough
to be trivial to assign registers. So this is not really surprising.

> I was wondering whether the implementation of qemu is tied to gcc or
> if it might be interesting to try to compile using IBM's compiler,
> which is able to generate Altivec code...

It might be possible with some work, but Altivec will not be useful
for the vast majority of instructions, basically only for MMX and
similar things, which AFAIK aren't yet supported in qemu.

-- 
	Falk

  reply	other threads:[~2004-08-02 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 12:07 [Qemu-devel] Performances on Mac OS X Laurent Amon
2004-08-02 12:20 ` Falk Hueffner [this message]
2004-08-02 13:02 ` Natalia Portillo
2004-08-02 13:38   ` Laurent Amon

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=87brhtohoh.fsf@informatik.uni-tuebingen.de \
    --to=hueffner@informatik.uni-tuebingen.de \
    --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).