From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg_temp_local_new should take no parameter
Date: Fri, 2 Jan 2009 04:36:01 +0000 [thread overview]
Message-ID: <200901020436.01777.paul@codesourcery.com> (raw)
In-Reply-To: <20090101143649.GA18298@miranda.arrow>
> The SH4 emulation seems to use 'plain' TCGv mostly, expects it to be
> 32-bits, and doesn't use the _tl macros, which I suppose is reasonable
> for a 32-bit only target.
>
> Alpha, ARM and M68K do something similar (so I'll try to follow the
> style that they use) but CRIS uses _tl a lot, which seems peculiar...
The distinction only really makes sense on CPUs that have both 32-bit and
64-bit variants. Chances are that if a 64-bit arm/m68k/cris cpu were to
exist then most of the code would need auditing anyway, so it's mostly a
matter of personal preference which is used.
Paul
prev parent reply other threads:[~2009-01-02 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 13:19 [Qemu-devel] [PATCH] tcg_temp_local_new should take no parameter Laurent Desnogues
2009-01-01 14:09 ` Aurelien Jarno
2009-01-01 14:36 ` Stuart Brady
2009-01-02 4:36 ` Paul Brook [this message]
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=200901020436.01777.paul@codesourcery.com \
--to=paul@codesourcery.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).