All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Marques de Souza <leonardo@ambientebrasil.com.br>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] (TEST) CFLAGS options + qemu 0.60
Date: Fri, 30 Jul 2004 16:13:57 -0300	[thread overview]
Message-ID: <410A9DF5.5080906@ambientebrasil.com.br> (raw)
In-Reply-To: <41096B3A.2090801@ambientebrasil.com.br>

Works great!

so im doing some benchmarks to see any general diference.
i trying PCMark 2002, any other sugestion?
I think the benchmark programs is a good choice to test virtual CPU, becouse
they use a lot of optimized intructions.


Well, when i use -mregpar=x, que qemu made a lot of 'booboos'. Some time 
start,
others guest Win98 and Linux crash...
not recomended for "production" hehe :P


Leonardo Marques de Souza wrote:

> Thanks!
>
> Im looking for
>
> I'll try to workarround compilation problem, doing it by hand,
> it happens only with help.c (well, all help.c in qemu tree)
>
> enter in i386 , i386-softemu , ppc-softemu
> and doing:
>
> gcc -Wall -O2 -march=pentium  -fno-strict-aliasing 
> -fomit-frame-pointer -I. -I/root/qemu-0.6.0/target-i386 
> -I/root/qemu-0.6.0 -D_GNU_SOURCE -I/root/qemu-0.6.0/slirp -c -o 
> helper.o /root/qemu-0.6.0/target-i386/helper.c
>
> just  return to root tree compilation and do make again to continue.
>
> I will see what instable qemu will be with -regparm=[1..3].  :)

  reply	other threads:[~2004-07-30 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 15:10 [Qemu-devel] (TEST) CFLAGS options + qemu 1.60 Leonardo Marques de Souza
2004-07-29 16:27 ` André Braga
2004-07-29 21:25   ` Leonardo Marques de Souza
2004-07-30 19:13     ` Leonardo Marques de Souza [this message]
2004-08-19 10:58       ` [Qemu-devel] (TEST) CFLAGS options + qemu 0.60 Piotr Krysik

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=410A9DF5.5080906@ambientebrasil.com.br \
    --to=leonardo@ambientebrasil.com.br \
    --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.