All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Natalia Portillo" <claunia@claunia.com>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Performances on Mac OS X
Date: Mon, 2 Aug 2004 14:02:48 +0100	[thread overview]
Message-ID: <E1BrcVy-00080f-CW@lists.gnu.org> (raw)
In-Reply-To: <1091448454.410e2e8606e5e@imp4-q.free.fr>

GCC supports Altivec, just see the help. 

> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org 
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org] 
> En nombre de Laurent Amon
> Enviado el: lunes, 02 de agosto de 2004 13:08
> Para: qemu-devel@nongnu.org
> Asunto: [Qemu-devel] Performances on Mac OS X
> 
> 
> Hello,
> 
> 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.
> 
> When compiling with -finline-functions, the generated 
> i386-softmmu/op.h is bad, and if you do not use it do compile 
> dyngen, there is no improvement.
> -Os actually decreases performance and I have not been able 
> to generate a profiled  executable with -fprofile-arcs.
> 
> Owners of PPC7450 or of G5 should try the relevant switch.
> 
> 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...
> 
> Lga.
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  parent reply	other threads:[~2004-08-02 13:06 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
2004-08-02 13:02 ` Natalia Portillo [this message]
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=E1BrcVy-00080f-CW@lists.gnu.org \
    --to=claunia@claunia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.