qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J.C. Pizarro" <jcpiza@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] What 64-bit CPU targets dominate in the future?
Date: Tue, 7 Aug 2007 02:36:37 +0200	[thread overview]
Message-ID: <998d0e4a0708061736w7166102uc0caa85cf0544f8d@mail.gmail.com> (raw)
In-Reply-To: <998d0e4a0708061637x4dfe0dew1edda6105e77a833@mail.gmail.com>

Hi people,

I'm looking for simulators of 64-bit processors for my 32-bit PC and
i've found one.

"qemu-system-x86_64" works simulating a x86-64 linux as slamd64, ubuntu, etc.

http://fabrice.bellard.free.fr/qemu/status.html indicates that x86-64
is OK for System emulation but is not supported for user emulation.

The problem is that the x86-64 ISA is too complex to develop i an
aplication that generates assembler or machine code like CacaoJVM,
JCVM, Flex, ...
x86-64 is CISC and not RISC. It will be easy if the 64-bit CPU is RISC.

I don't know what 64-bit CPU that will dominate in years 2008 .. 2013.

I'm not sure if PearPC or PSIM simulates PowerPC64 ISA but the
"Full-System Simulator for IBM PowerPC 970" said that it does but it's
closed source.

I'm not sure if Sulima simulates Sparc64 ISA from
http://ccnuma.anu.edu.au/sulima/0.4/sparc-sulima-0.4.tar.gz but it
goes to v0.4 version, not v1.0 :(

The IA-64 CPU is monstruous and too complex because there aren't known
open source applications that target IA-64. I don't know if that
simulator exists or not.

After talking, my question is:

What popularity of CPU will dominate in the years 2008 .. 2013? By example,
1. x86-64: 75%
2. ppc64: 15%
3. sparc64: 5%
4. others: 5%

Any opinion to the respect?

Sincerely yours, J.C.

       reply	other threads:[~2007-08-07  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <998d0e4a0708061637x4dfe0dew1edda6105e77a833@mail.gmail.com>
2007-08-07  0:36 ` J.C. Pizarro [this message]
2007-08-08 14:03   ` [Qemu-devel] What 64-bit CPU targets dominate in the future? Paul Brook

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=998d0e4a0708061736w7166102uc0caa85cf0544f8d@mail.gmail.com \
    --to=jcpiza@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).