On Wed, May 09, 2007 at 06:25:01PM +0200, Johannes Schindelin wrote: > None. I only suspected them to be carried out in byte order. From what I > know, there are some shifts involved, which might or might not be helped > by 32-bit arithmetic. > > I did not really look into it. > > From my prior debugging experiences on Intel, though, I automatically > looked for the least significant bytes at the beginning of those "sha1" > variables, and came up empty. So, I'm confused about what you actually mean by "big endian" here. I originally assumed that you meant that SHA1's are defined as bit arrays, and that the first bit of the SHA1 is in the high-order bit of the first byte. But if you just meant that the first byte of the SHA1 is stored in the first byte of the array... that kind of goes without saying, doesn't it? In any case, maybe this is a detail that's best left to the code itself. --b. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
