From: Stefan Weil <sw@weilnetz.de>
To: Richard Henderson <rth@twiddle.net>
Cc: blauwirbel@gmail.com, borntraeger@de.ibm.com,
qemu-devel@nongnu.org, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH] tcg: Introduce TCGReg for all TCG hosts (fixes build for s390 hosts)
Date: Fri, 07 Oct 2011 20:26:53 +0200 [thread overview]
Message-ID: <4E8F446D.1090102@weilnetz.de> (raw)
In-Reply-To: <4E8F4133.9000404@twiddle.net>
Am 07.10.2011 20:13, schrieb Richard Henderson:
> On 10/07/2011 11:00 AM, Stefan Weil wrote:
>> +#define TCGReg int /* TODO: Remove this line when tcg-target.c uses
>> TCGReg. */
>
> Nack. This is too ugly to live.
>
> How hard can it be to simply change the prototype in each
> of the backend files instead? Yes, full conversion to
> TCGReg is desirable, but this is not C++ -- integers and
> enums are interchangable without casts.
>
> r~
The goal of my patch is to get code which compiles again
on all hosts with minimum risk and which is a base for further
improvements.
I cannot run build tests for all possible hosts, and even
changing 4 prototypes for each host is a risk when it is not
tested. Yes, you can review the changes, some developers can
try builds, but that takes a lot of time.
As soon as my patch is applied, it is possible to add
more TCGReg usage to tcg.c, s390/tcg-target.c and all
other TCG targets in independent patches.
I'm just preparing patches for tcg.c and i386/tcg-target.*.
But let me repeat: these new patches need a good review
which will take some time. The bug fix should be applied soon.
Maybe you can change your mind and send an ack.
- Stefan
next prev parent reply other threads:[~2011-10-07 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 18:00 [Qemu-devel] [PATCH] tcg: Introduce TCGReg for all TCG hosts (fixes build for s390 hosts) Stefan Weil
2011-10-07 18:13 ` Richard Henderson
2011-10-07 18:26 ` Stefan Weil [this message]
2011-10-08 10:30 ` Blue Swirl
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=4E8F446D.1090102@weilnetz.de \
--to=sw@weilnetz.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.