From: David Hildenbrand <david@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, Cornelia Huck <cohuck@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v1] s390x/tcg: Don't model FP registers as globals
Date: Mon, 4 Feb 2019 14:30:16 +0100 [thread overview]
Message-ID: <4c7fd460-2b5c-b109-cbc7-6d2bb242df99@redhat.com> (raw)
In-Reply-To: <a34065d4-b06e-2157-e89d-be30adf87ed0@linaro.org>
On 04.02.19 14:27, Richard Henderson wrote:
> On 1/31/19 2:37 PM, David Hildenbrand wrote:
>> As floating point registers overlay some vector registers and we want
>> to make use of the general tcg_gvec infrastructure that assumes vectors
>> are not stored in globals but in memory, don't model flaoting point
>> registers as globals anymore. This is than similar to how arm handles
>> it.
>>
>> Reading/writing a floating point register means reading/writing memory now.
>>
>> Break up ugly in2_x2() handling that modifies both, in1 and in2 into
>> in1_x2l and in2_x2h. This makes things more readable. Also, in1_x1() is
>> ugly as it touches out/out2, get rid of that and use prep_x1() instead.
>>
>> As we are no longer able to use the original global variables for
>> out/out2, we have to use new temporary variables and write from them to
>> the target registers using wout_ helpers.
>>
>> E.g. an instruction that reads and writes x1 will use
>> - prep_x1 to get the values into out/out2
>> - wout_x1 to write the values from out/out2
>> This special handling is needed for x1 as it is often used along with
>> other inputs, so in1/in2 is already used.
>>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> ---
>> target/s390x/insn-data.def | 150 ++++++++++++++++++-------------------
>> target/s390x/translate.c | 133 +++++++++++++++++++-------------
>> 2 files changed, 158 insertions(+), 125 deletions(-)
>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Thanks!
I'll probably switch naming of in1_x2l and in2_x2h to
in1_x2h and in2_x2l (will double check, but I guess this is the right
thing to do - high double word always comes first, e.g. in memory).
>
>
> r~
>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2019-02-04 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 14:37 [Qemu-devel] [PATCH v1] s390x/tcg: Don't model FP registers as globals David Hildenbrand
2019-02-04 13:27 ` Richard Henderson
2019-02-04 13:30 ` David Hildenbrand [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=4c7fd460-2b5c-b109-cbc7-6d2bb242df99@redhat.com \
--to=david@redhat.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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).