From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: [Qemu-devel] [PULL 07/12] target-i386: Define MMREG_UNION macro
Date: Thu, 21 Jan 2016 13:09:36 -0200 [thread overview]
Message-ID: <1453388981-24807-8-git-send-email-ehabkost@redhat.com> (raw)
In-Reply-To: <1453388981-24807-1-git-send-email-ehabkost@redhat.com>
This will simplify the definitions of ZMMReg and MMXReg.
Reviewed-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
target-i386/cpu.h | 27 +++++++++++----------------
1 file changed, 11 insertions(+), 16 deletions(-)
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index b41ce82..70cf66d 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -725,23 +725,18 @@ typedef struct SegmentCache {
uint32_t flags;
} SegmentCache;
-typedef union {
- uint8_t _b[64];
- uint16_t _w[32];
- uint32_t _l[16];
- uint64_t _q[8];
- float32 _s[16];
- float64 _d[8];
-} ZMMReg;
+#define MMREG_UNION(bits) \
+ union { \
+ uint8_t _b[(bits)/8]; \
+ uint16_t _w[(bits)/16]; \
+ uint32_t _l[(bits)/32]; \
+ uint64_t _q[(bits)/64]; \
+ float32 _s[(bits)/32]; \
+ float64 _d[(bits)/64]; \
+ }
-typedef union {
- uint8_t _b[8];
- uint16_t _w[4];
- uint32_t _l[2];
- uint64_t _q[1];
- float32 _s[2];
- float64 _d[1];
-} MMXReg;
+typedef MMREG_UNION(512) ZMMReg;
+typedef MMREG_UNION(64) MMXReg;
typedef struct BNDReg {
uint64_t lb;
--
2.1.0
next prev parent reply other threads:[~2016-01-21 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 15:09 [Qemu-devel] [PULL 00/12] X86 queue, 2016-01-21 Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 01/12] target-i386: Rename optimize_flags_init() Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 02/12] target-i386/ops_sse.h: Use MMX_Q macro Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 03/12] target-i386: Use a _q array on MMXReg too Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 04/12] target-i386: Rename struct XMMReg to ZMMReg Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 05/12] target-i386: Rename XMM_[BWLSDQ] helpers to ZMM_* Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 06/12] target-i386: Define MMXReg._d field Eduardo Habkost
2016-01-21 15:09 ` Eduardo Habkost [this message]
2016-01-21 15:09 ` [Qemu-devel] [PULL 08/12] target-i386: Add suffixes to MMReg struct fields Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 09/12] target-i386: Fallback vcpu's TSC rate to value returned by KVM Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 10/12] target-i386: Reorganize TSC rate setting code Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 11/12] target-i386: Add support to migrate vcpu's TSC rate Eduardo Habkost
2016-01-21 15:09 ` [Qemu-devel] [PULL 12/12] target-i386: Add PKU and and OSPKE support Eduardo Habkost
2016-01-21 17:19 ` [Qemu-devel] [PULL 00/12] X86 queue, 2016-01-21 Peter Maydell
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=1453388981-24807-8-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).