From: Eray Ozkural <examachine@gmail.com>
To: Niki Yoshiuchi <aplusbi@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Fixed-point arithmetic on 32-bit architectures
Date: Wed, 5 Jan 2011 20:38:13 +0200 [thread overview]
Message-ID: <AANLkTik6hCnLnhBBNxY1S_-q8rDir-fCHhiS9Fkbn5pk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimLJma0A+nnuCeSX0sVPXpbiALOtOUN2uzRwNfo@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2568 bytes --]
Hi there,
Thank you for your reply Niki.
The range of numbers is usually between 0 and 1, because I'm mostly working
on
normalized vectors.
I was using 22 bits for the decimal part but unfortunately multiplication is
a common operation. I was converting to Int64 for multiplication. I thought
about half-shifting but then I didn't try it because I thought there might
be lost
precision, on second thought it might work for me though, perhaps I can
define
it as another (risky) operation. Right-shifting each operand 11 bits before
multiplication
would save me from using any Int64 ops, or if I am certain that each operand
is
smaller than 1 I could shift right fewer bits initially to save some
precision. A
good way to do that would be to have an assert that gets turned on in debug
builds.
The safe multiplication was defined as:
let mul x y =
Int64.to_int
(Int64.shift_right
(Int64.mul (Int64.of_int x) (Int64.of_int y) ) q)
where q = 22 for me.
On Wed, Jan 5, 2011 at 6:34 PM, Niki Yoshiuchi <aplusbi@gmail.com> wrote:
> What range of numbers are you hoping to represent and what operations
> are you commonly performing on them? If it's possible for you to
> represent your numbers as 24.8 fixed-point (for example) and you are
> mostly adding and subtracting, then I would recommend using 32 bit
> integers and casting to 64 bit for multiplication and division.
> Alternatively you can try and be clever about your shifting instead of
> casting (shifting the multiplicand instead of the product, or doing a
> half shift on each multiplicand, etc).
>
> On Wed, Jan 5, 2011 at 11:22 AM, Eray Ozkural <examachine@gmail.com>
> wrote:
> > Hello there,
> > I'm using fixed-point arithmetic in an algorithm. I am troubled by the
> > inefficiency of the fixed-point multiplication and division operations on
> > 32-bit architectures. On the Intel 64-bit architecture, I can use the
> > Nativeint module and it's quite fast, on 32-bit I had to use the Int64
> > module (for the necessary shifts and mul/div's) and I encountered a
> > significant slowdown, naturally. is there a preferred way of performing
> > fixed point arithmetic with ocaml on 32-bit architectures that I might be
> > overlooking?
> > Best,
> > --
> > Eray Ozkural, PhD candidate. Comp. Sci. Dept., Bilkent University,
> Ankara
> > http://groups.yahoo.com/group/ai-philosophy
> >
> >
>
--
Eray Ozkural, PhD candidate. Comp. Sci. Dept., Bilkent University, Ankara
http://groups.yahoo.com/group/ai-philosophy
http://myspace.com/arizanesil http://myspace.com/malfunct
[-- Attachment #2: Type: text/html, Size: 3570 bytes --]
prev parent reply other threads:[~2011-01-05 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 16:22 Eray Ozkural
2011-01-05 16:34 ` Niki Yoshiuchi
2011-01-05 18:38 ` Eray Ozkural [this message]
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=AANLkTik6hCnLnhBBNxY1S_-q8rDir-fCHhiS9Fkbn5pk@mail.gmail.com \
--to=examachine@gmail.com \
--cc=aplusbi@gmail.com \
--cc=caml-list@inria.fr \
/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