Download raw body.
MurmurHash2 unaligned access
Stefan Sperling:
> Our hash input (SHA1 has object ID) is an uint8_t array type.
> Should we change the type of the key argument to uint8_t * or is the
> cast from void * to unsigned char * safe?
I feel confident that it's safe:
void *
memcpy(void *dst0, const void *src0, size_t length)
{
char *dst = dst0;
const char *src = src0;
...
> It seems 'data' will be
> accessed in multiples of 4. I don't know sparc64 alignement
> requirements off the top of my head. Is 4 or 8 required?
Natural alignment, i.e., sizeof(type).
memcpy() should be fine. The alternative is some << | << | << |
monstrosity.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
MurmurHash2 unaligned access