From: "Andreas Färber" <andreas.faerber@web.de>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 0/6] target-i386: TCGv cleanups
Date: Mon, 12 Dec 2011 16:34:14 +0100 [thread overview]
Message-ID: <4EE61EF6.9040501@web.de> (raw)
In-Reply-To: <201112121456.30527.paul@codesourcery.com>
Am 12.12.2011 15:56, schrieb Paul Brook:
>> Am 12.12.2011 00:42, schrieb Paul Brook:
>>>> This series makes target-i386 compile with DEBUG_TCGV_TL.
>>>
>>> What benefit does this provide?
>>
>> It showcases what changes would need to be done to allow type-safe
>> compilation of the first pair of --enable-system targets.
>
> How is the existing code not type safe? What benefit does making TCGv a
> separate type rather than an alias for either _i32 or _i64 give?
I've already answered that extensively elsewhere.
Look, I really personally don't care about i386 and whether this RFC
gets applied to target-i386 or not. This is an example, because the
changes that I *do* care about have already been folded into my branch,
with the help of my TCGv series now posted for others' benefit.
Please read the other thread for details of what it does and doesn't do.
Andreas
prev parent reply other threads:[~2011-12-12 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 12:58 [Qemu-devel] [RFC 0/6] target-i386: TCGv cleanups Andreas Färber
2011-12-10 12:58 ` [Qemu-devel] [PATCH 1/6] target-i386: Fix sloppy uses of i32/i64 functions Andreas Färber
2011-12-10 12:58 ` [Qemu-devel] [PATCH 2/6] target-i386: Cleanup movd xmm, ea Andreas Färber
2011-12-10 12:58 ` [Qemu-devel] [RFC 3/6] tcg: Add tcg_gen_qemu_{ld,st}64_tl() Andreas Färber
2011-12-10 12:58 ` [Qemu-devel] [RFC 4/6] target-i386: Use tcg_gen_{ld,st}64_tl() Andreas Färber
2011-12-10 12:58 ` [Qemu-devel] [RFC 5/6] target-i386: Cleanup pinsrq Andreas Färber
2011-12-10 12:58 ` [Qemu-devel] [RFC 6/6] target-i386: Cleanup pextrq Andreas Färber
2011-12-11 23:42 ` [Qemu-devel] [RFC 0/6] target-i386: TCGv cleanups Paul Brook
2011-12-12 9:50 ` Andreas Färber
2011-12-12 14:56 ` Paul Brook
2011-12-12 15:34 ` Andreas Färber [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=4EE61EF6.9040501@web.de \
--to=andreas.faerber@web.de \
--cc=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).