From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch Submission] QEMU with GCC/Win32
Date: Sat, 30 Jul 2005 23:28:19 +0200 [thread overview]
Message-ID: <46d6db660507301428707a9acf@mail.gmail.com> (raw)
In-Reply-To: <42EBD7E3.7090409@steveperkins.net>
First rule of (efficient) engineering: <<if it is not broken,
do not try to fix it>>
for the record: gcc-3.3-x is *fine* and *most* stable,
not just on windows. It's still my reference compiler
even for linux kernels.
Why do you feel it's necessary to upgrade? Because
gcc people do? There's *no* speed improvement, as
far as I can see (well, it crashes faster :))
This is not a C++ based project.
Now that for the first time on win XP hosts we get
decent speed, unless patches are really a must, I do
not intend personnally to upgrade at every snapshot
my current version of qemu.
And testing does not mean using the latest only.
We're talking stability/reliability now that we have
kqemu in the picture (taking care of speed improvement).
I believe reporting each pb is a team effort. Fabrice
never reports any pb, he fixes them efficiently at his
own pace.
In short: there is a team out there. Or this mailing list
would be dead.
Christian
next prev parent reply other threads:[~2005-07-30 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 18:42 [Qemu-devel] [Patch Submission] QEMU with GCC/Win32 Steve D. Perkins
2005-07-30 19:13 ` Paul Brook
2005-07-30 19:41 ` Steve D. Perkins
2005-07-30 21:16 ` Filip Navara
2005-07-30 21:28 ` Christian MICHON [this message]
2005-07-30 23:04 ` Steve D. Perkins
2005-07-30 23:04 ` Paul Brook
2005-07-30 23:16 ` Steve D. Perkins
2005-07-30 23:39 ` Paul Brook
2005-08-01 11:34 ` Gwenole Beauchesne
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=46d6db660507301428707a9acf@mail.gmail.com \
--to=christian.michon@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 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.