From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Cc: Sunil Amitkumar Janki <psychicistnonconformist@gmail.com>
Subject: Re: [Qemu-devel] 0.9.0 and svn don't build with -march=pentium2 etc.; was: Latest SVN fails to build on Fedora Core 6 (same with 0.9.0)
Date: Sat, 24 Mar 2007 12:55:16 +0000 [thread overview]
Message-ID: <200703241255.16524.jseward@acm.org> (raw)
In-Reply-To: <46051A67.6060300@gmail.com>
> As far as X86 is concerned i386/i486/i586 are very different from later
> generation
> processors. I am wondering whether another host and target architecture
> could be
> created called i686 that makes use of something like MMX or other
> registers in Intel
> Pentium II/III/4 and AMD Athlon to negate the lack of general purpose
> registers.
I don't see how. MMX/SSE is suitable for SIMD processing of media data
and to some extent for floating point, but is largely unusable for ad-hoc
integer computation, especially anything that involves address calculations.
> The fact that QEMU works and can be optimised on x86_64 is the only
> saving grace
> for the architecture, that is still suffering from a lack of registers
> compared to any
> other architecture.
The lack of registers isn't ideal, but it's not a big deal, and in the
grand scheme of things x86_64 has a lot going for it. The most
important of which are that (from the software side) all the hard-won
knowledge of how to compile good code for x86 carries across more or less
directly to x86_64, and (from the hardware side) hardware people already
know how to make fast, cheap x86s, so it's easy to move to making fast,
cheap x86_64s.
The problems of the gcc backend to qemu have already been discussed
extensively on this list. Stealing 3+ registers from gcc on x86 really
is asking for trouble, and I believe it is generally understood that the
best long term solution is to move to a self-contained back end that
does not use gcc for dynamic code generation.
J
next prev parent reply other threads:[~2007-03-24 13:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 13:37 [Qemu-devel] Latest SVN fails to build on Fedora Core 6 (same with 0.9.0) Thomas Orgis
2007-03-18 4:45 ` Tony Nelson
2007-03-18 8:37 ` Thomas Orgis
2007-03-18 9:18 ` Nigel Horne
2007-03-22 19:46 ` [Qemu-devel] 0.9.0 and svn don't build with -march=pentium2 etc.; was: " Thomas Orgis
2007-03-22 20:13 ` Sunil Amitkumar Janki
2007-03-23 9:58 ` Thomas Orgis
2007-03-23 10:21 ` Sunil Amitkumar Janki
2007-03-23 15:45 ` Paul Brook
2007-03-23 20:11 ` Thomas Orgis
2007-03-24 12:32 ` Sunil Amitkumar Janki
2007-03-24 12:55 ` Julian Seward [this message]
2007-03-26 9:34 ` Thomas Orgis
2007-03-28 19:56 ` Rob Landley
2007-03-29 10:55 ` Thomas Orgis
2007-03-29 14:55 ` [Qemu-devel] QEMU Alpha target Stuart Brady
2007-03-29 15:08 ` Paul Brook
2007-03-29 15:12 ` Stuart Brady
2007-03-29 15:25 ` Paul Brook
2007-03-29 21:01 ` J. Mayer
2007-03-29 15:25 ` [Qemu-devel] 0.9.0 and svn don't build with -march=pentium2 etc.; was: Latest SVN fails to build on Fedora Core 6 (same with 0.9.0) Sunil Amitkumar Janki
2007-03-29 16:08 ` Stuart Brady
2007-03-29 19:57 ` J. Mayer
2007-03-29 20:04 ` Brian Wheeler
2007-03-29 21:18 ` [Qemu-devel] QEMU Alpha target Stuart Brady
2007-03-29 21:31 ` J. Mayer
2007-03-29 21:57 ` Stuart Brady
2007-03-29 21:48 ` Thomas Orgis
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=200703241255.16524.jseward@acm.org \
--to=jseward@acm.org \
--cc=psychicistnonconformist@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).