Previously, calculated hashes would be wrong if input length was a multiple of 8.
An example of such a wrong hash calculation is the string "content/audio/wep_colony_shotgun".
Using the current upstream version, the hash is wrongly calculated as cc54dec1972bc218. The correct hash for this string is d8a50cd49f4b1c59, which this patched version produces.
Previously, calculated hashes would be wrong if input length was a multiple of 8.
An example of such a wrong hash calculation is the string "content/audio/wep_colony_shotgun". Using the current upstream version, the hash is wrongly calculated as cc54dec1972bc218. The correct hash for this string is d8a50cd49f4b1c59, which this patched version produces.