qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: gang.chen.5i5j@gmail.com
Subject: [Qemu-devel] [PATCH 01/14] target-tilegx: Use V1 in simd_helper.c
Date: Thu,  1 Oct 2015 12:38:33 +1000	[thread overview]
Message-ID: <1443667126-6257-2-git-send-email-rth@twiddle.net> (raw)
In-Reply-To: <1443667126-6257-1-git-send-email-rth@twiddle.net>

This will tidy up lots of cases where we'll want
to replicate a byte across the 8 elements of the word.

Signed-off-by: Richard Henderson <rth@twiddle.net>
---
 target-tilegx/simd_helper.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/target-tilegx/simd_helper.c b/target-tilegx/simd_helper.c
index b931929..774def4 100644
--- a/target-tilegx/simd_helper.c
+++ b/target-tilegx/simd_helper.c
@@ -23,12 +23,16 @@
 #include "exec/helper-proto.h"
 
 
+/* Broadcast a value to all elements of a vector.  */
+#define V1(X)      (((X) & 0xff) * 0x0101010101010101ull)
+
+
 uint64_t helper_v1shl(uint64_t a, uint64_t b)
 {
     uint64_t m;
 
     b &= 7;
-    m = 0x0101010101010101ULL * (0xff >> b);
+    m = V1(0xff >> b);
     return (a & m) << b;
 }
 
@@ -37,7 +41,7 @@ uint64_t helper_v1shru(uint64_t a, uint64_t b)
     uint64_t m;
 
     b &= 7;
-    m = 0x0101010101010101ULL * ((0xff << b) & 0xff);
+    m = V1(0xff << b);
     return (a & m) >> b;
 }
 
-- 
2.4.3

  reply	other threads:[~2015-10-01  2:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01  2:38 [Qemu-devel] [PATCH 00/14] Collected tilegx patches Richard Henderson
2015-10-01  2:38 ` Richard Henderson [this message]
2015-10-01  2:38 ` [Qemu-devel] [PATCH 02/14] target-tilegx: Implement v*shl, v*shru, and v*shrs instructions Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 03/14] target-tilegx: Implement v*add and v*sub instructions Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 04/14] target-tilegx: Implement v1multu instruction Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 05/14] target-tilegx: Implement crc instructions Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 06/14] target-tilegx: Implement table index instructions Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 07/14] target-tilegx: Implement complex multiply instructions Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 08/14] target-tilegx: Let x1 pipe process bpt instruction only Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 09/14] linux-user/syscall_defs.h: Sync the latest si_code from Linux kernel Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 10/14] linux-user/tilegx: Implement tilegx signal features Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 11/14] target-tilegx: Decode ill pseudo-instructions Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 12/14] target-tilegx: Use TILEGX_EXCP_SIGNAL instead of TILEGX_EXCP_SEGV Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 13/14] target-tilegx: Fix a typo for mnemonic about "ld_add" Richard Henderson
2015-10-01  2:38 ` [Qemu-devel] [PATCH 14/14] target-tilegx: Handle nofault prefetch instructions Richard Henderson
     [not found] ` <560D3DC0.7010500@hotmail.com>
2015-10-01 14:04   ` [Qemu-devel] [PATCH 00/14] Collected tilegx patches Chen Gang

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=1443667126-6257-2-git-send-email-rth@twiddle.net \
    --to=rth@twiddle.net \
    --cc=gang.chen.5i5j@gmail.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).