From: Richard Zidlicky <rz@linux-m68k.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SPARC - host support in vl.c
Date: Wed, 1 Sep 2004 17:44:21 +0200 [thread overview]
Message-ID: <20040901154421.GB13876@linux-m68k.org> (raw)
In-Reply-To: <873c23x8dk.fsf@informatik.uni-tuebingen.de>
On Wed, Sep 01, 2004 at 12:14:47AM +0200, Falk Hueffner wrote:
> "Bochnig, Martin" <mb1x@gmx.com> writes:
>
> > Here my patch suggestions to add SPARC host support to vl.c :
> >
> > #elif defined(__sparc__)
>
> Why conditionalize this to __sparc__? Seems like a generally sensible
> fallback.
Fabrice had plans to do this properly, by counting executed
instructions.
Any idea what happened with this plan?
Richard
next prev parent reply other threads:[~2004-09-01 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 22:04 [Qemu-devel] SPARC - host support in vl.c Bochnig, Martin
2004-08-31 22:14 ` Falk Hueffner
2004-08-31 22:24 ` Bochnig, Martin
2004-08-31 22:41 ` Falk Hueffner
2004-09-01 7:57 ` Bochnig, Martin
2004-09-01 15:44 ` Richard Zidlicky [this message]
2004-08-31 23:24 ` [Qemu-devel] The very best I can get on SPARC Bochnig, Martin
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=20040901154421.GB13876@linux-m68k.org \
--to=rz@linux-m68k.org \
--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).