On Sun, Jul 08, 2012 at 10:08:15PM +0100, Mindaugas Rasiukevicius wrote:
> Joerg Sonnenberger wrote:
> > > Log Message:
> > > Add MurmurHash2 -- a non-cryptographic hash function by Austin Appleby.
> > > The code is taken from the upstream and is in the public domain.
> > >
> > > OK christos@
> >
Mindaugas Rasiukevicius wrote:
> Simon Burge wrote:
> > > > > Are you referring to the weakness when using 4-bytes?
> > > > > Anyway, that is why the file name does not have 2 in it, so that we
> > > > > could add MurmurHash3 as well.
> > > >
> > > > That's completely different to the other hashe
Simon Burge wrote:
> > > > Are you referring to the weakness when using 4-bytes?
> > > > Anyway, that is why the file name does not have 2 in it, so that we
> > > > could add MurmurHash3 as well.
> > >
> > > That's completely different to the other hashes we have in the source
> > > tree. Can yo
Mindaugas Rasiukevicius wrote:
> Simon Burge wrote:
> > Mindaugas Rasiukevicius wrote:
> > > Simon Burge wrote:
> > > >
> > > > > [ ... ]
> > > > >
> > > > > Log Message:
> > > > >
> > > > > Add MurmurHash2 -- a non-cryptographic hash function by Austin
> > > > > Appleby. The code is taken fr
On Sun, Jul 08, 2012 at 20:14:13 +, David Laight wrote:
> Log Message:
> The MDP_USEDFPU (amd64 and sh3) and MDP_SSTEP (sh3) are lwp flags not
> process ones, rename to MDL_xxx.
While you are at it... according to
$ gid -r '^MDP_' | grep 'l_md.*[&|]='
there are also
amd64: MDP_IRET
Joerg Sonnenberger wrote:
> > Log Message:
> > Add MurmurHash2 -- a non-cryptographic hash function by Austin Appleby.
> > The code is taken from the upstream and is in the public domain.
> >
> > OK christos@
>
> There are a number of issues with this. First of all, it pollutes the
> global name
On Sun, Jul 08, 2012 at 01:21:12AM +, Mindaugas Rasiukevicius wrote:
> Module Name: src
> Committed By: rmind
> Date: Sun Jul 8 01:21:12 UTC 2012
>
> Modified Files:
> src/common/lib/libc: Makefile.inc
> src/lib/libc: shlib_version
> src/lib/libc/hash: Makefile.inc
Simon Burge wrote:
> Mindaugas Rasiukevicius wrote:
>
> > Simon Burge wrote:
> > >
> > > > [ ... ]
> > > >
> > > > Log Message:
> > > >
> > > > Add MurmurHash2 -- a non-cryptographic hash function by Austin
> > > > Appleby. The code is taken from the upstream and is in the public
> > > > dom
Mindaugas Rasiukevicius wrote:
> Simon Burge wrote:
> >
> > > [ ... ]
> > >
> > > Log Message:
> > >
> > > Add MurmurHash2 -- a non-cryptographic hash function by Austin Appleby.
> > > The code is taken from the upstream and is in the public domain.
> >
> > I'm curious why you've chosen Murm
Hi Simon,
Simon Burge wrote:
>
> > [ ... ]
> >
> > Log Message:
> >
> > Add MurmurHash2 -- a non-cryptographic hash function by Austin Appleby.
> > The code is taken from the upstream and is in the public domain.
>
> I'm curious why you've chosen MurmurHash2 instead of MurmurHash3 given the
On Mon, Jul 09, 2012 at 12:48:32AM +1000, Simon Burge wrote:
> > Add MurmurHash2 -- a non-cryptographic hash function by Austin Appleby.
> > The code is taken from the upstream and is in the public domain.
>
> I'm curious why you've chosen MurmurHash2 instead of MurmurHash3 given the
> known probl
"Mindaugas Rasiukevicius" wrote:
> [ ... ]
>
> Log Message:
>
> Add MurmurHash2 -- a non-cryptographic hash function by Austin Appleby.
> The code is taken from the upstream and is in the public domain.
I'm curious why you've chosen MurmurHash2 instead of MurmurHash3 given the
known problems w
For what it's worth, it would appear that the problem with the
t_nat_exec tests is due to the use of the -b option in ipftest.
This apparently is supposed to produce only "brief" output, with a
pass/fail/nomatch indication. However, the "golden" test output files
appear to contain detailed ou
13 matches
Mail list logo
