qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v1 01/46] target/loongarch: Add LASX data type XReg


From: Richard Henderson
Subject: Re: [PATCH v1 01/46] target/loongarch: Add LASX data type XReg
Date: Tue, 20 Jun 2023 14:09:27 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0

On 6/20/23 11:37, Song Gao wrote:
diff --git a/target/loongarch/cpu.h b/target/loongarch/cpu.h
index b23f38c3d5..347950b4d0 100644
--- a/target/loongarch/cpu.h
+++ b/target/loongarch/cpu.h
@@ -259,9 +259,23 @@ typedef union VReg {
      Int128   Q[LSX_LEN / 128];
  }VReg;
+#define LASX_LEN (256)
+typedef union XReg {
+    int8_t   XB[LASX_LEN / 8];
+    int16_t  XH[LASX_LEN / 16];
+    int32_t  XW[LASX_LEN / 32];
+    int64_t  XD[LASX_LEN / 64];
+    uint8_t  UXB[LASX_LEN / 8];
+    uint16_t UXH[LASX_LEN / 16];
+    uint32_t UXW[LASX_LEN / 32];
+    uint64_t UXD[LASX_LEN / 64];
+    Int128   XQ[LASX_LEN / 128];
+} XReg;

This is following the example of target/i386, and I think it is a bad example.

For Arm, we have one ARMVectorReg which covers AdvSIMD (128-bit) and SVE 
(2048-bit).
I would prefer if you just expand the definition of VReg to be 256 bits.



r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]