caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: Thomas Braibant <thomas.braibant@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Hashing failure
Date: Fri, 21 Dec 2012 16:58:45 +0900	[thread overview]
Message-ID: <A522CC99-4B97-45AB-A9DF-418363FB0716@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <CAHR=Vkx3hntWcQYV8tptKnrRyKHNBdfA-6KxjfxWEp=j4Q-saQ@mail.gmail.com>

On 2012/12/21, at 5:18, Thomas Braibant <thomas.braibant@gmail.com> wrote:

> Hi list,
> 
> I have a piece of code that looks like this.
> 
> let hkey = H.hash d in (* a custom hash function *)
> let index = hkey mod (Array.length t.table) in
> let bucket = t.table.(index) in (* 1 *)
> 
> the line marked with 1 was generating an index out of bounds
> exception. It appeared that it was because index was negative, a
> problem  I knew of when using mod ... So I added an abs around index
> 
> let hkey = H.hash d in
> let index =  abs (hkey mod (Array.length t.table)) in
> let bucket = t.table.(index) in (* 1 *)
> 
> But it yields the same exception...
> 
> This seemed completely unbelievable, till I realized that
> - x mod y may return a negative value if x is less than 0
> - abs x may return a negative value if x is min_int

What about just ensuring that your hash function returns a positive
value to start with.
An easy way to do that is

   let hkey = hkey land max_int

This avoids using abs altogether.
(I now understand why the standard hash function is 30-bit…)

	Jacques Garrigue

  parent reply	other threads:[~2012-12-21  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHR=VkzBhR5FMsWO-_BVzYV4yhSARP8rg7G3b=jezU6OOOg0jQ@mail.gmail.com>
2012-12-20 20:18 ` Thomas Braibant
2012-12-20 20:32   ` [Caml-list] " Thomas Braibant
2012-12-20 21:01     ` Martin Jambon
2012-12-21  7:58   ` Jacques Garrigue [this message]
2012-12-21 10:02   ` [Caml-list] " Xavier Leroy
2012-12-21 19:03     ` Martin Jambon

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=A522CC99-4B97-45AB-A9DF-418363FB0716@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@inria.fr \
    --cc=thomas.braibant@gmail.com \
    /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).