[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, hash, created. v0.6.1-545-ge9c717e

From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, hash, created. v0.6.1-545-ge9c717e
Date: Thu, 09 Apr 2009 04:56:02 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU PSPP".

The branch, hash has been created
        at  e9c717e43278364a49b68db4718cab5c9229c8fb (commit)

- Log -----------------------------------------------------------------
commit e9c717e43278364a49b68db4718cab5c9229c8fb
Author: Ben Pfaff <address@hidden>
Date:   Wed Apr 8 21:55:31 2009 -0700

    Use Bob Jenkins lookup3 hash instead of FNV.
    The Jenkins lookup3 hash is superior to FNV in collision resistance,
    avalanching, and performance on systems that do not have fast
    multiplication.  It also provides a good way to combine the result of
    a previous hashing step with the current hash, using its "basis" argument.
    This commit replaces the PSPP implementation of FNV with the Jenkins
    lookup3 hash and updates all the current users.
    In addition, John Darrington pointed out that commit dd2e61b4a
    "Make create_iconv() properly distinguish converters by name"
    unintentionally introduced gratuitous hash collisions, by causing
    all converters where tocode and fromcode were the same to hash to
    value 0, and converters where tocode and fromcode were swapped to
    hash to the same value as each other.  Using the "basis" argument to
    the Jenkins hash properly, instead of just attempting to combine
    hash values with XOR, fixes this problem.

commit b4e3275011982e29b80589bef705fc8a0a0316dd
Author: Ben Pfaff <address@hidden>
Date:   Wed Apr 8 21:39:22 2009 -0700

    NPAR TESTS: Consistently order variables in summary statistics.
    The set of variables in the NPAR TESTS specs structure was ordered
    randomly, according to however the hash function happened to arrange them.
    Sort them by variable name, instead, so that they always appear in
    alphabetical order in, e.g., descriptive statistics output.
    The particular hash function PSPP uses now tends to order variables
    alphabetically anyhow.  The next commit changes the PSPP hash functions,
    so fixing this in advance prevents having to update any test output.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]