caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ken Rose <kenrose@tfb.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml, int32/64, bigarray and unsigned values ...
Date: Wed, 13 Apr 2005 11:28:58 -0700	[thread overview]
Message-ID: <425D64EA.2020105@tfb.com> (raw)
In-Reply-To: <20050411153551.GA10362@pegasos>

Sven Luther wrote:

> Yeah, bit shifting should be ok, since the sign is ignored for those.

But be careful about right shifts, which are different signed than 
unsigned.  Signed repeats the sign bit, while unsigned shifts in zeroes. 
  If you mask afterwards, it should be fine.

  - ken


  parent reply	other threads:[~2005-04-13 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11  7:46 Sven Luther
2005-04-11 12:57 ` [Caml-list] " Eric Cooper
2005-04-11 15:35   ` Sven Luther
2005-04-11 16:13     ` Eric Cooper
2005-04-13  6:54     ` Florian Hars
2005-04-13 18:28     ` Ken Rose [this message]
2005-05-25  6:06     ` partition tables and ocaml Taras
2005-05-25  9:09       ` Sven Luther
2005-04-12 17:19   ` [Caml-list] ocaml, int32/64, bigarray and unsigned values Paul Snively

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=425D64EA.2020105@tfb.com \
    --to=kenrose@tfb.com \
    --cc=caml-list@inria.fr \
    --cc=rose@acm.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).