From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU fails with different levels of compiler optimizati
Date: Thu, 29 Jul 2004 17:01:05 -0300 [thread overview]
Message-ID: <2ad73a040729130164240863@mail.gmail.com> (raw)
In-Reply-To: <BAY7-F13E4D3MBhe3WY0002c20e@hotmail.com>
Uh... Not yet, but you have a point: it makes it more likely that the
critical code will fit the cache. I did not enable
-fomit-frame-pointer because it makes debugging a *pain in the rear*,
and sometimes I run QEMU under GDB just to see if I can narrow the
problem down to some specific part of the code. And so far it seems
that the mingw runtime breaks something with the Windows timing
functions if I run higher levels of optimization. I'm yet to try it
under Linux.
On Wed, 28 Jul 2004 16:36:38 +0000, Tom Musgrove
<tommusgrove__@hotmail.com> wrote:
> Have you tried to optimize for size instead?
>
> Ie -Os (and also -fomit-frame-pointer)
>
> It sometimes creates more speed optimal code than the other optimization
> flags.
>
--
"A year spent in artificial intelligence is enough to make one believe in God"
Alan J. Perlis
prev parent reply other threads:[~2004-07-29 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 16:36 [Qemu-devel] Re: QEMU fails with different levels of compiler optimizati Tom Musgrove
2004-07-29 20:01 ` André Braga [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=2ad73a040729130164240863@mail.gmail.com \
--to=meianoite@gmail.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).