qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH, RFC, WIP] TCG for Qemu target Sparc32/64
Date: Fri, 22 Feb 2008 18:13:40 +0200	[thread overview]
Message-ID: <f43fc5580802220813n33c40366ma161e9f4bfc271b4@mail.gmail.com> (raw)
In-Reply-To: <20080222000605.GB6462@networkno.de>

On 2/22/08, Thiemo Seufer <ths@networkno.de> wrote:
> Blue Swirl wrote:
>  > The attached patch enables most TCG ops for Qemu Sparc32/64 target.
>  > Sparc32 softmmu and linux-user are OK, but Sparc64 and Sparc32plus
>  > targets do not work.
>  >
>  > Comments?
>  >
>  > It would be nice to get rid of T2 usage in std (also stda and
>  > casa/casxa) but I don't know how to pass a 64-bit value from legacy op
>  > to TCG stores and loads on a 32-bit target and host.

[cut]

>  This whole lot should probably move to generic code (conditionalized on
>  TARGET_LONG_BITS), I have the same code in my MIPS prototype.

I agree. Also these lines, if they are really needed:
+#if TCG_TARGET_REG_BITS == 32
+#define tcg_gen_ld_ptr tcg_gen_ld_i32
+#else
+#define tcg_gen_ld_ptr tcg_gen_ld_i64
+#endif

  reply	other threads:[~2008-02-22 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 20:27 [Qemu-devel] [PATCH, RFC, WIP] TCG for Qemu target Sparc32/64 Blue Swirl
2008-02-22  0:06 ` Thiemo Seufer
2008-02-22 16:13   ` Blue Swirl [this message]
2008-02-23 18:23 ` [Qemu-devel] " Fabrice Bellard
2008-02-23 18:29   ` Blue Swirl
2008-02-23 18:48     ` Fabrice Bellard
2008-02-23 20:32   ` Paul Brook
2008-02-23 23:59   ` Stuart Brady

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=f43fc5580802220813n33c40366ma161e9f4bfc271b4@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ths@networkno.de \
    /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).