From: Alexander Graf <agraf@suse.de>
To: Filip Navara <filip.navara@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Win64 host port
Date: Sat, 1 Aug 2009 18:31:30 +0200 [thread overview]
Message-ID: <A82A8552-018B-4607-A41C-0D6774292955@suse.de> (raw)
In-Reply-To: <5b31733c0908010441t70134f2ascb0d7be8e09c44b1@mail.gmail.com>
On 01.08.2009, at 13:41, Filip Navara wrote:
> Hi,
>
> for anyone interested I have pushed my Win64 host port of QEMU to
> git://repo.or.cz/qemu/navara.git. I'm eventually planning to clean it
> up and submit it as patches, but I have already way too long patch
> queue now. Only i386 and ARM targets were tested and it is as stable
> as the Win32 port.
Wow, congratulations!
How did you get around the sizeof(ulong) != sizeof(void*) problems?
Alex
next prev parent reply other threads:[~2009-08-01 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 11:41 [Qemu-devel] Win64 host port Filip Navara
2009-08-01 16:31 ` Alexander Graf [this message]
2009-08-01 16:39 ` Filip Navara
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=A82A8552-018B-4607-A41C-0D6774292955@suse.de \
--to=agraf@suse.de \
--cc=filip.navara@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).