The j602 version is correct, and the same code is used in each. The problem seems to be that the code was designed for 32 bit integers.
Note also that the reference C implementation based on RFC 1321 (http://www.rfc-editor.org/rfc/rfc1321.txt) gives exactly the same results on 32 bit and 64 bit machines. (In other words it gives the same wrong result when compiled with -m64 that J64-802 gives.) So that means I can't just use a C implementation of md5sum compiled with -m64 to work around this issue (and I can't link to C code compiled with -m32 from 64 bit J). Solvable, certainly, but annoying... Thanks, -- Raul On Sat, Sep 6, 2014 at 9:21 AM, Skip Cave <s...@caveconsulting.com> wrote: > Wow! I wonder which hash is the correct md5 hash? Where did the code for > each of them come from? > > Skip > > Skip Cave > Cave Consulting LLC > > > On Sat, Sep 6, 2014 at 8:10 AM, Raul Miller <rauldmil...@gmail.com> wrote: > >> j602: >> >> load'convert/misc/md5' >> md5 'example' >> 1a79a4d60de6718e8e5b326e338ae533 >> >> j64-802: >> >> load'convert/misc/md5' >> md5 'example' >> 64a9df64d8defee229d86709a425ea7a >> >> This is a problem... >> >> == >> Raul >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
