in reply to Re^2: Creating custom hash of file
in thread Creating custom hash of file

Hmm, well, it's going to be hard to get rid of 'bigint' if you want 64-bit arithmetic to work correctly :(

If your perl doesn't know about pack 'q', then you can roll it yourself with the following, but it will be even slower:

use strict; use warnings; use Fcntl ':seek'; use bigint; use constant CHUNK => 65536; sub calc { my $file = shift or die "no filename given\n"; my $hash = -s $file; my $chunk = CHUNK; $hash < $chunk and die "$file is too small ($hash bytes < $chunk)\ +n"; open my $in, '<', $file or die "Cannot open $file for input: $!\n" +; local $/ = \$chunk; my @val = unpack 'L*' , readline($in); for (my $j = 0; $j < $#val; $j += 2) { $hash += ($val[$j] << 32) + $val[$j+1]; $hash &= 2 ** 64 - 1; } seek($in, SEEK_END, -$chunk); @val = unpack 'L*' , readline($in); for (my $j = 0; $j < $#val; $j += 2) { $hash += ($val[$j] << 32) + $val[$j+1]; $hash &= 2 ** 64 - 1; } close $in; return sprintf '%016x', $hash; } open my $out, '>', 'test.deleteme'; print $out ' ' x (65536*4); close $out; print calc('test.deleteme'), $/;

Perl's probably not the best language for this. The code is much shorter than the other languages, which is usually the case for a given algorithm, but the performance is horrible. You really want to do yourself a favour and run this stuff on a 64 bit architecture.

Maybe there's another monk who's into numerical analysis and can spot an insight, but it's beyond my ken.

• another intruder with the mooring in the heart of the Perl

Replies are listed 'Best First'.
Re^4: Creating custom hash of file
by 2ge (Scribe) on Mar 18, 2007 at 12:13 UTC
    thank you, it is more and more closer to the python code (read on wiki page I posted in first message, maybe it will help you). Also, funny thing is, when I try your latest code it is terrible slow (but thats OK as you wrote), but I get different hash. I have:
    This is perl, v5.8.4 built for MSWin32-x86-multi-thread (with 3 registered patches, see perl -V for more detail) perlhash.pl 00000000ffffffff
    When you run this, you get different hash?