From: Aurelien Jarno <aurelien@aurel32.net>
To: "Gibbons, Scott" <sgibbons@qualcomm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] VLIW?
Date: Wed, 16 Jun 2010 17:54:38 +0200 [thread overview]
Message-ID: <20100616155438.GA384@hall.aurel32.net> (raw)
In-Reply-To: <2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A46216@NASANEXMB07.na.qualcomm.com>
On Tue, Jun 15, 2010 at 08:53:26AM -0700, Gibbons, Scott wrote:
> Has anyone done a port of QEMU to a VLIW architecture? I'm interested in seeing what was done.
>
The git version of QEMU is working on IA64, which is an EPIC CPU, but
can be considered as certain kind of VLIW CPU.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-06-16 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 15:53 [Qemu-devel] VLIW? Gibbons, Scott
2010-06-16 15:54 ` Aurelien Jarno [this message]
2010-06-16 17:41 ` Richard Henderson
2010-06-17 15:12 ` Gibbons, Scott
2010-06-17 16:02 ` Richard Henderson
2010-06-17 18:05 ` Gibbons, Scott
2010-06-17 18:14 ` Richard Henderson
2010-06-17 18:24 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2010-06-15 22:57 Gibbons, Scott
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=20100616155438.GA384@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=sgibbons@qualcomm.com \
/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).