From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] TCG debugging improvements
Date: Mon, 17 Nov 2008 14:45:40 +0000 [thread overview]
Message-ID: <200811171445.40710.paul@codesourcery.com> (raw)
I'd just applied changes that enforce type size checking for TCG variables
when DEBUG_TCGV is defined. This should help avoid subtle bugs due to
64/32-bit mismatches.
I fixed a few bugs in the process, but it's mostly mechanical changes. TCGv
is target_ulong sized, so the majority of code remains unchanged. Explicit
sizes are typically only required when working with different sized ops, or
floating point.
One of the main side-effects of this is that helper functions now need to be
declared properly. Previously we sort-of did this, but not consistently
enough to enforce types. With the exception of the SSE/MMX ops (which are
table driven and use messy typecasts) we should be able to detect
inconsistencies between the code generator and the helper function
implementations.
There should be no functional changes. I've tested what I can, but please
test your favourite host/target.
Paul
next reply other threads:[~2008-11-17 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 14:45 Paul Brook [this message]
2008-11-17 20:08 ` [Qemu-devel] TCG debugging improvements Blue Swirl
2008-11-17 21:00 ` Andreas Färber
2008-11-18 9:39 ` Aurelien Jarno
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=200811171445.40710.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).