qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>, patches@linaro.org
Subject: [Qemu-devel] [RFC] bitops: Provide sext32() and sext64() for signextending bitfields
Date: Thu, 27 Jun 2013 16:47:42 +0100	[thread overview]
Message-ID: <1372348062-4516-1-git-send-email-peter.maydell@linaro.org> (raw)

A common operation in instruction decoding is to take a field
from an instruction that represents a signed integer in some
arbitrary number of bits, and sign extend it into a C signed
integer type for manipulation. Provide new functions sext32()
and sext64() to abstract away the bit manipulation.

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
I think we've vaguely tossed around the idea of a function to
abstract away the concept of doing a signextension before,
so here's an RFC...

Does the API look right? The other approach I thought of would
be to have functions sextract32()/sextract64() which work like
the existing extract{32,64} but return signed (and sign
extended) values, but providing the raw sign-extension separately
seemed more flexible. (If we want the sextract ops then we could
implement them as sext32(extract32(value, start, length), length).)

This implementation continues to rely on the behaviour of right-shift
of signed integers (as do most of the places which open-code this
operation today; see also HACKING section 6). If we decide in future
that we'd rather do this in a strictly-portable way we'll have a
single place we need to change.

(PS: Not really very tested yet :-))

 include/qemu/bitops.h |   40 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)

diff --git a/include/qemu/bitops.h b/include/qemu/bitops.h
index affcc96..5c6a756 100644
--- a/include/qemu/bitops.h
+++ b/include/qemu/bitops.h
@@ -273,4 +273,44 @@ static inline uint64_t deposit64(uint64_t value, int start, int length,
     return (value & ~mask) | ((fieldval << start) & mask);
 }
 
+/**
+ * sext32:
+ * @value: value to sign-extend
+ * @length: length of the bitfield in value
+ *
+ * Sign-extend the least significant @length bits in @value to
+ * a 32 bit signed integer. That is to say, bits [0..@length-2]
+ * are untouched, and bit [@length-1] is duplicated into all
+ * higher bits of the returned value.
+ *
+ * Returns: the sign-extended value of the bitfield.
+ */
+static inline int32_t sext32(uint32_t value, int length)
+{
+    /* Note that this implementation relies on right shift of signed
+     * integers being an arithmetic shift.
+     */
+    return ((int32_t)(value << (32 - length))) >> length;
+}
+
+/**
+ * sext64:
+ * @value: value to sign-extend
+ * @length: length of the bitfield in value
+ *
+ * Sign-extend the least significant @length bits in @value to
+ * a 64 bit signed integer. That is to say, bits [0..@length-2]
+ * are untouched, and bit [@length-1] is duplicated into all
+ * higher bits of the returned value.
+ *
+ * Returns: the sign-extended value of the bitfield.
+ */
+static inline int64_t sext64(uint64_t value, int length)
+{
+    /* Note that this implementation relies on right shift of signed
+     * integers being an arithmetic shift.
+     */
+    return ((int64_t)(value << (64 - length))) >> length;
+}
+
 #endif
-- 
1.7.9.5

             reply	other threads:[~2013-06-27 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 15:47 Peter Maydell [this message]
2013-06-27 16:35 ` [Qemu-devel] [RFC] bitops: Provide sext32() and sext64() for signextending bitfields Richard Henderson
2013-06-27 17:58 ` Markus Armbruster
2013-06-27 18:03   ` 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=1372348062-4516-1-git-send-email-peter.maydell@linaro.org \
    --to=peter.maydell@linaro.org \
    --cc=patches@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).